X-Git-Url: https://juplo.de/gitweb/?p=hibernate4-maven-plugin;a=blobdiff_plain;f=src%2Fsite%2Fxhtml%2Fforce.xhtml;h=ee3586f74a216676c2e01db19ce800449a4e5132;hp=cd582db3d5c854be187a813d5cf42ec1dd8fe4d9;hb=149a94d09dfb678e4be39aefb20dbf86ef28c416;hpb=4940080670944a15916c68fb294e18a6bfef12d5 diff --git a/src/site/xhtml/force.xhtml b/src/site/xhtml/force.xhtml index cd582db3..ee3586f7 100644 --- a/src/site/xhtml/force.xhtml +++ b/src/site/xhtml/force.xhtml @@ -4,22 +4,24 @@ +

Force Execution

The hibernate-maven-plugin computes MD5-sums for all found annotated classes and stores them together with the generated schema. If no classes were changed or added and the dialect wasn't changed too, it - automatically skips the configured schema-export, to speed up the development - cycle. + automatically skips the configured SQL-generation — and more + important in this respect — the execution of the generated SQL, + to speed up the development cycle.

The plugin signals, that the execution was skipped by setting the maven - property $\{hibernate.export.skipped\} to true. + property ${hibernate.schema.skipped} to true. This may be helpful, because other plugins like dbunit-plugin may fail, when the execution is skipped.

- If you need the hibernate-maven-plugin to <never skip execution automatically>, + If you need the hibernate-maven-plugin to never skip execution automatically, you can force it to do so, if you set the parameter force to true:

@@ -33,7 +35,7 @@ </configuration> </plugin>

- Or you may specify -Dhibernate.export.force=true at the command line, + Or you may specify -Dhibernate.schema.force=true at the command line, if you want to force hibernate-maven-plugin only once.