X-Git-Url: http://juplo.de/gitweb/?p=hibernate4-maven-plugin;a=blobdiff_plain;f=src%2Fsite%2Fapt%2Fpitfalls.apt;h=33c40cfafb88cc43acf9422eb05ce85b2d2ce563;hp=24909a5cc2ff02307ca63c4500a4996bc1cb0a5b;hb=84e8517be79d88d7e2bec2688a8f965f591394bf;hpb=f27134cdec6c38b4c8300efb0bb34fc8ed381033 diff --git a/src/site/apt/pitfalls.apt b/src/site/apt/pitfalls.apt index 24909a5c..33c40cfa 100644 --- a/src/site/apt/pitfalls.apt +++ b/src/site/apt/pitfalls.apt @@ -1,6 +1,10 @@ -Known Pitfalls + --- + Known Pitfalls + --- + Kai Moritz + --- -* hibernate4-maven-plugin always needs a database-connection +hibernate4-maven-plugin always needs a database-connection 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 @@ -17,7 +21,7 @@ Known Pitfalls But even when no database is to be created, hibernate always needs to know the dialect. Hence, the plugin will fail if this parameter is missing! -* Dependency for driver-class XYZ is missing +Dependency for driver-class XYZ is missing One regular problem is the scope of the jdbc-driver-dependency. It is very unlikely, that this dependency is needed at compile-time. @@ -81,7 +85,7 @@ Known Pitfalls Because otherwise, this dependency will unnecessarily bloat the runtime-dependencies of your project. -* DBUnit {fails} after execution of hibernate4 was skipped because nothing has changed +DBUnit {fails} after execution of hibernate4 was skipped because nothing has changed If hibernate4-maven-plugin skips its excecution, this may lead to errors in other plugins. @@ -113,7 +117,7 @@ Known Pitfalls ------------ -* The database will not be recreated after a manual drop/clean +The database will not be recreated after a manual drop/clean If one manually drops the database or removes the hsqldb-files, it will not be recreated by the hibernate4-maven-plugin, because it cannot detect, that @@ -135,7 +139,7 @@ Known Pitfalls mvn hibernate4:export -Dhibernate.export.force=true ------------- -* The hibernate4:export goal is not executed, when tests are skipped +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 @@ -153,4 +157,4 @@ mvn hibernate4:export -Dhibernate.export.force=true ------------ 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 + page {{{./skip.html}To skip or not to skip: that is the question}}...