Upgraded scannotation from 1.0.3 to 1.0.4

This fixes the bug that occures on some platforms, if the path contains a
space. Created a fork of scannotation to bring the latest bug-fixes from SVN
to maven central...

diff --git a/pom.xml b/pom.xml
index 0a8572d..b536886 100644 (file)
--- a/pom.xml
+++ b/pom.xml
@@ -132,7 +132,7 @@
     <el-api.version>3.0.0</el-api.version>
     <maven.version>3.3.3</maven.version>
     <maven-plugin-log4j.version>1.0.1</maven-plugin-log4j.version>
-    <scannotation.version>1.0.3</scannotation.version>
+    <scannotation.version>1.0.4</scannotation.version>
   </properties>
 
   <dependencies>
@@ -173,7 +173,7 @@
       <version>${el-api.version}</version>
     </dependency>
     <dependency>
-      <groupId>org.scannotation</groupId>
+      <groupId>de.juplo</groupId>
       <artifactId>scannotation</artifactId>
       <version>${scannotation.version}</version>
     </dependency>

diff --git a/src/site/xhtml/pitfalls.xhtml b/src/site/xhtml/pitfalls.xhtml
index 9b86800..7183929 100644 (file)
--- a/src/site/xhtml/pitfalls.xhtml
+++ b/src/site/xhtml/pitfalls.xhtml
@@ -184,19 +184,12 @@ mvn hibernate4:export -Dhibernate.export.force=true</pre>
     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.
+    directory, you are expiriencing a bug, in the scannotation-library, that
+    was closed in version 1.1.0 of the hibernate-maven-plugin.
   </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.
+      You should consider to upgrade to that version of the plugin.
     </strong>
   </p>
  </body>