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.
- This can be achieved with the commandline-parameter
+ This can be achieved with the command-line parameter
<<<-Dhibernate.export.target=SCRIPT>>> or with the following configuration:
------------
the configuration nor the annotated classes have changed, because an
unnecessary drop-create-cycle might take a long time. The plugin will
report that like this:
+
-------------
[INFO] No modified annotated classes found and dialect unchanged.
[INFO] Skipping schema generation!
-[------------
+-------------
- If one always uses <<<mvn clen>>> for cleanup, this will not happen.
- Otherwise the recreation must be forced:
+ If one always uses <<<mvn clean>>> for cleanup, this will not happen.
+ Otherwise the recreation must be {{{./force.html}forced}}:
-------------
mvn hibernate4:export -Dhibernate.export.force=true
-------------
+
+* The hibernate4:export goal is not executed, when tests are skipped
+
+ The hibernate4-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>
+ ...
+ <configuration>
+ <skip>false</skip>
+ </configuration>
+</plugin>
+------------
+
+ Background-information for this design-decission can be found on the extra
+ page {{{./skip.html}To skip or not to skip: that is the question}}...
\ No newline at end of file