CORAL-116 fail early with readable message when no db table is defined.
Removed Maven 1 build files and Maven 1 Coral plugin
Set dbTable property before handlerClass, to allow correct handler
initialization.
Version bump
Sonar upgrade
CORAL-119: don't bail when no tuple is found in the database. It's a
valid situation when all non-builtin attributes of the relevant class
are optional and all are undefined for a specific resource instance.
CORAL-120: skip data deletion if parent class is not tabular or does not
have concrete attributes.
CORAL-121: make SQL script generation optional
consider actual type of ModificationItem in comparison
Added toString implementations for debugging
Revert "consider actual type of ModificationItem in comparison"

This reverts commit 753d6e84f199d696514a6efdd1b105eca364325e.
CORAL-122: don't consider resources as changed when they are not
physically inside project basedir. BuildContext.hasDelta() always
returns true for those which causes an inifinte build loop.
CORAL-123: preserve data loaded by handlers earlier in the sequence
CORAL-123: pick up only data for the selected resource classes (this way
GenericResourceHandler specific data is ignored)
CORAL-116: issue SQL DML statements to the underlying database when
DB TABLE / DB COLUMN are modified in Coral Schema.
CORAL-124: adjusted test
Added index on coral_resource(created_by) to allow counting resources
created by users efficiently.
Merge branch 'dev' into master - Release 1.0.16