Added FAQ-entry for problem with whitespaces in the path under Windows

[hibernate4-maven-plugin] / src / site / xhtml / pitfalls.xhtml

diff --git a/src/site/xhtml/pitfalls.xhtml b/src/site/xhtml/pitfalls.xhtml
index 5000695..9b86800 100644 (file)
--- a/src/site/xhtml/pitfalls.xhtml
+++ b/src/site/xhtml/pitfalls.xhtml
@@ -151,7 +151,7 @@ mvn hibernate4:export -Dhibernate.export.force=true</pre>
   executed, you can configure that explicitly like this:
   </p>
   <pre class="prettyprint linenums lang-html">
-&gt;plugin&lt;
+&lt;plugin&gt;
   &lt;groupId&gt;de.juplo&lt;/groupId&gt;
   &lt;artifactId&gt;hibernate4-maven-plugin&lt;/artifactId&gt;
   ...
@@ -163,5 +163,41 @@ mvn hibernate4:export -Dhibernate.export.force=true</pre>
   Background-information for this design-decission can be found on the extra
   page <a href="./skip.html">To skip or not to skip: that is the question</a>...
   </p>
+  <h2>I do not want my dependencies to be scanned for hibernate annotations</h2>
+  <p>
+    If you do not want your dependencies to be scanned for hibernate annotations,
+    you can pass <code>-Dhibernate.export.scan_dependencies=none</code> to maven
+    or set <code>scanDependencies</code> to <code>none</code> in the configuration
+    of the plugin like this:
+  </p>
+  <pre class="prettyprint linenums lang-html">
+&lt;plugin&gt;
+  &lt;groupId&gt;de.juplo&lt;/groupId&gt;
+  &lt;artifactId&gt;hibernate4-maven-plugin&lt;/artifactId&gt;
+  ...
+  &lt;configuration&gt;
+    &lt;scanDependencies&gt;none&lt;/scanDependencies&gt;
+  &lt;/configuration&gt;
+&lt;/plugin&gt;</pre>
+  <h2>No annotated classes found</h2>
+  <p>
+    If you are working under Windows and get the error-message
+    <code>No annotated classes found in directory C:\projects\X Y Z\path-to-project\target\classes</code>,
+    but you are really sure, that there are annotated classes in that
+    directory, you should try to rename your folders, so that their names
+    do not contain any whitespaces.
+  </p>
+  <p>
+    So fare, I got to bug-reports considering this.
+    In both cases, removing all whitespaces from the path solved the error.
+    In both cases, I was not able to reproduce the bug on my development
+    system, which is running under linux.
+  </p>
+  <p>
+    <strong>
+      Hence, I assume, this is a sublte bug in the way, the java-version for
+      Windows is handling paths, that contain whitespaces.
+    </strong>
+  </p>
  </body>
 </html>