- hibernate4-maven-plugin by default scans dependencies in the scope
+ hibernate-maven-plugin by default scans dependencies in the scope
compile. You can configure it to scan dependencies in other
scopes as well. But it scans only direct dependencies. Transitive
dependencies are not scanned for annotated classes. If some of your
annotated classes are hidden in a transitive dependency, you can simply
add that dependency explicitly.
- The default-configuration uses the EXPORT-target of the SchemaExport-Tool.
- If you do not need to create a database with the evaluated schema, you can
- use the NONE- or the SCRIPT-target.
+ The default-configuration executes the created SQL.
+ Therefore, it needs a valid database-connection and fails, if none is
+ available.
+ If you do not need the generated SQL to be executed automatically,
+ you can set the property hibernate.schema.execute to
+ false.
This can be achieved with the command-line parameter
- -Dhibernate.export.target=SCRIPT or with the following configuration:
+ -Dhibernate.schema.execute=false or with the following
+ configuration:
<configuration> - <target>SCRIPT</target> + <execute>false</execute> </configuration>
But even when no database is to be created, hibernate always needs to know - the dialect. Hence, the plugin will fail if this parameter is missing! + the dialect. Hence, the plugin will still fail, if this parameter is also + missing!
@@ -36,7 +42,7 @@
So a tidy maven-developer would usually scope it for runtime.
- But this will break the execution of the hibernate4-maven-plugin.
+ But this will break the execution of the hibernate-maven-plugin.
Since it will not be able to see the needed dependency, it will fail with
an error-message like:
A quick workaround for this error would be, to delete the runtime-constraint for the jdbc-driver-dependency. @@ -70,12 +87,13 @@
<plugin>
<groupId>de.juplo</groupId>
- <artifactId>hibernate4-maven-plugin</artifactId>
+ <artifactId>hibernate-maven-plugin</artifactId>
<version>${project.version}</version>
<executions>
<execution>
<goals>
- <goal>export</goal>
+ <goal>drop</goal>
+ <goal>create</goal>
</goals>
</execution>
</executions>
@@ -93,42 +111,42 @@
Because otherwise, this dependency will unnecessarily bloat the
runtime-dependencies of your project.
- DBUnit fails after execution of hibernate4 was skipped because nothing has changed
+ DBUnit fails after execution of hibernate was skipped because nothing has changed
- If hibernate4-maven-plugin skips its excecution, this may lead to errors in
+ If hibernate-maven-plugin skips its excecution, this may lead to errors in
other plugins.
For example, when importing sample-data in the automatically created database
with the help of the dbunit-plugin,
the CLEAN_INSERT-operation may fail because of foreign-key-constraints,
- if the database was not recreated, because the hibernate4-maven-plugin has
+ if the database was not recreated, because the hibernate-maven-plugin has
skipped its excecution.
A quick fix to this problem is, to force
- hibernate4-maven-plugin to export the schema every time it is running.
+ hibernate-maven-plugin to generate and execute the SQL every time it is running.
But to recreate the database on every testrun may noticeable slow down your
development cycle, if you have to wait for slow IO.
- To circumvent this problem, hibernate4-maven-plugin signals a skipped
- excecution by setting the maven property $\{hibernate.export.skipped\} to
+ To circumvent this problem, hibernate-maven-plugin signals a skipped
+ excecution by setting the maven property ${hibernate.schema.skipped} to
true.
You can configure other plugins to react on this signal.
For example, the dbunit-plugin can be configured to skip its excecution, if
- hibernate4-maven-plugin was skipped like this:
+ hibernate-maven-plugin was skipped like this:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>dbunit-maven-plugin</artifactId>
<configuration>
- <skip>${hibernate.export.skipped}</skip>
+ <skip>${hibernate.schema.skipped}</skip>
</configuration>
</plugin>
The database will not be recreated after a manual drop/clean
If one manually drops the database or removes the hsqldb-files, it will not
- be recreated by the hibernate4-maven-plugin, because it cannot detect, that
+ be recreated by the hibernate-maven-plugin, because it cannot detect, that
the database needs to be recreated.
This happens, because the plugin will not recreate the database if neither
the configuration nor the annotated classes have changed, because an
@@ -143,17 +161,17 @@
Otherwise the recreation must be forced:
-mvn hibernate4:export -Dhibernate.export.force=true
- The hibernate4:export goal is not executed, when tests are skipped
+mvn hibernate:create -Dhibernate.schema.force=true
+
- The hibernate4-maven-plugin automatically skips its execution, when
+ The hibernate-maven-plugin automatically skips its execution, when
maven.test.skip is set to true. If you need it to be always
executed, you can configure that explicitly like this:
<plugin>
<groupId>de.juplo</groupId>
- <artifactId>hibernate4-maven-plugin</artifactId>
+ <artifactId>hibernate-maven-plugin</artifactId>
...
<configuration>
<skip>false</skip>
@@ -166,14 +184,14 @@ mvn hibernate4:export -Dhibernate.export.force=true
If you do not want your dependencies to be scanned for hibernate annotations,
- you can pass -Dhibernate.export.scan_dependencies=none to maven
+ you can pass -Dhibernate.schema.scan.dependencies=none to maven
or set scanDependencies to none in the configuration
of the plugin like this:
<plugin>
<groupId>de.juplo</groupId>
- <artifactId>hibernate4-maven-plugin</artifactId>
+ <artifactId>hibernate-maven-plugin</artifactId>
...
<configuration>
<scanDependencies>none</scanDependencies>
@@ -184,20 +202,50 @@ mvn hibernate4:export -Dhibernate.export.force=true
If you are working under Windows and get the error-message
No annotated classes found in directory C:\projects\X Y Z\path-to-project\target\classes,
but you are really sure, that there are annotated classes in that
- directory, you should try to rename your folders, so that their names
- do not contain any whitespaces.
-
- - So fare, I got to bug-reports considering this. - In both cases, removing all whitespaces from the path solved the error. - In both cases, I was not able to reproduce the bug on my development - system, which is running under linux. + directory, you are expiriencing a bug, in the scannotation-library, that + was closed in version 1.1.0 of the hibernate-maven-plugin.
- Hence, I assume, this is a sublte bug in the way, the java-version for - Windows is handling paths, that contain whitespaces. + You should consider to upgrade to the latest version of the plugin.
+
+ If you specify two goals, for example drop and
+ create, each goal has to be specified in its own
+ execution, so that you can specify two different
+ output-files for the two goals.
+ Otherwise, both goals will use the same output-file and the goal, that
+ is run second, will always skip, becaus it will find, that the output
+ file already exists and conclude, that its work was already done in a
+ prior run.
+
+ Example configuration for two goals: +
++<executions> + <execution> + <id>Create Drop-Schema</id> + <phase>test-compile</phase> + <goals> + <goal>drop</goal> + </goals> + <configuration> + <outputFile>db-schema/drop-schema.ddl</outputFile> + </configuration> + </execution> + <execution> + <id>Create Create-Schema</id> + <phase>test-compile</phase> + <goals> + <goal>create</goal> + </goals> + <configuration> + <outputFile>db-schema/create-schema.ddl</outputFile> + </configuration> + </execution> +</executions>