X-Git-Url: https://juplo.de/gitweb/?p=website;a=blobdiff_plain;f=dist%2Fhibernate4-maven-plugin-1.0.2%2Fforce.html;fp=dist%2Fhibernate4-maven-plugin-1.0.2%2Fforce.html;h=0000000000000000000000000000000000000000;hp=8d09713e930a3e9b86867cb143614c4184724a85;hb=b293b312d6f0dd8b2dc716375fd442dd295a9942;hpb=9179a67d9952d3b63e95686dbd6cacd3c9e13cb2 diff --git a/dist/hibernate4-maven-plugin-1.0.2/force.html b/dist/hibernate4-maven-plugin-1.0.2/force.html deleted file mode 100644 index 8d09713e..00000000 --- a/dist/hibernate4-maven-plugin-1.0.2/force.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - - - - - juplo - Hibernate 4 Maven Plugin - Force Exceution - - - - - - - - - - - - - - -
- - -
-
-

Hibernate 4 Maven Plugin - Force Exceution

-
-

Force execution

-

The hibernate4-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.

-

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

-

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

-
-
<plugin>
-  <groupId>de.juplo</groupId>
-  <artifactId>hibernate4-maven-plugin</artifactId>
-  <version>${project.version}</version>
-  <configuration>
-    <force>true</force>
-  </configuration>
-</plugin>
-

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

-
-
- -

- - Built by Maven - -

-
-
- -
-