X-Git-Url: https://juplo.de/gitweb/?p=hibernate4-maven-plugin;a=blobdiff_plain;f=src%2Fsite%2Fxhtml%2Fpitfalls.xhtml;h=90e09241b60291774dbe854ae30483c86bb1b584;hp=50006953f49f302c55157ea5aa97f1fc90454e57;hb=473c3ef285c19e0f0b85643b67bbd77e06c0b926;hpb=74c0dd783b84c90e116f3e7f1c8d6109845ba71f diff --git a/src/site/xhtml/pitfalls.xhtml b/src/site/xhtml/pitfalls.xhtml index 50006953..90e09241 100644 --- a/src/site/xhtml/pitfalls.xhtml +++ b/src/site/xhtml/pitfalls.xhtml @@ -151,7 +151,7 @@ mvn hibernate4:export -Dhibernate.export.force=true executed, you can configure that explicitly like this:

->plugin<
+<plugin>
   <groupId>de.juplo</groupId>
   <artifactId>hibernate4-maven-plugin</artifactId>
   ...
@@ -163,5 +163,21 @@ mvn hibernate4:export -Dhibernate.export.force=true
Background-information for this design-decission can be found on the extra page To skip or not to skip: that is the question...

+

I do not want my dependencies to be scanned for hibernate annotations

+

+ If you do not want your dependencies to be scanned for hibernate annotations, + you can pass -Dhibernate.export.scan_dependencies=none to maven + or set scanDependencies to none in the configuration + of the plugin like this: +

+
+<plugin>
+  <groupId>de.juplo</groupId>
+  <artifactId>hibernate4-maven-plugin</artifactId>
+  ...
+  <configuration>
+    <scanDependencies>none</scanDependencies>
+  </configuration>
+</plugin>