X-Git-Url: https://juplo.de/gitweb/?p=hibernate4-maven-plugin;a=blobdiff_plain;f=src%2Fsite%2Fapt%2Fforce.apt;fp=src%2Fsite%2Fapt%2Fforce.apt;h=26554d1a0334d13a69f0474017998f4b45a98518;hp=0000000000000000000000000000000000000000;hb=4b507b15b0122ac180e44b8418db8d9143ae9c3a;hpb=65bbbdbaa7df1edcc92a3869122ff06a3895fe57 diff --git a/src/site/apt/force.apt b/src/site/apt/force.apt new file mode 100644 index 00000000..26554d1a --- /dev/null +++ b/src/site/apt/force.apt @@ -0,0 +1,31 @@ +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 <<>>. + This may be helpful, because other plugins like + {{{http://mojo.codehaus.org/dbunit-maven-plugin/}dbunit-plugin}} + {{{./pitfalls.html#fails}may fail}}, when the execution is skipped. + + If you need the hibernate4-maven-plugin to + execution, you can force it to do so, if you set the parameter <<>> to + <<>>: + +---------------- + + de.juplo + hibernate4-maven-plugin + ${project.version} + + true + + +---------------- + + Or you may specify <<<-Dhibernate.export.force=true>>> at the command line, + if you want to force hibernate4-maven-plugin only once.