X-Git-Url: https://juplo.de/gitweb/?p=hibernate4-maven-plugin;a=blobdiff_plain;f=src%2Fsite%2Fapt%2Fpitfalls.apt;h=24909a5cc2ff02307ca63c4500a4996bc1cb0a5b;hp=61b5bc955ed74c57b878e770238886ddb4d77340;hb=d38b2386641c7ca00f54d69cb3f576c20b0cdccc;hpb=1ba817af3ae5ab23232fca001061f8050cecd6a7 diff --git a/src/site/apt/pitfalls.apt b/src/site/apt/pitfalls.apt index 61b5bc95..24909a5c 100644 --- a/src/site/apt/pitfalls.apt +++ b/src/site/apt/pitfalls.apt @@ -5,7 +5,7 @@ Known Pitfalls 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: ------------ @@ -122,14 +122,35 @@ Known Pitfalls 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 <<>> for cleanup, this will not happen. - Otherwise the recreation must be forced: + If one always uses <<>> 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 + <<>> is set to <<>>. If you need it to be always + executed, you can configure that explicitly like this: + +------------ + + de.juplo + hibernate4-maven-plugin + ... + + false + + +------------ + + 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