Hi all, is it only my setup or is there a problem if there is a colon in the project path? I attached a small sample project. (I hope it's allowed to attach files...)
I'm using Maven 3 and tried it on Mac OS X (10.6.5) and on Ubuntu Linux. To reproduce the problem: 1. Untar the attached project somewhere. 2. Try "mvn test". 3. Everything works like expected. 4. Do "mvn clean". 5. Rename some parent directory (or the project directory itself) to something containing a colon (for example from "colon_issue" to "colon:issue"). 6. Retry "mvn test". 7. It shows a compilation error and, of course, gives you a build failure. The error message looks something like this: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project colon_issue: Compilation failure [ERROR] issue/src/test/java/org/example/colon_issue/FooTest.java:[11,30] cannot find symbol [ERROR] symbol : class Foo [ERROR] location: class org.example.colon_issue.FooTest Looks like it splits the path to the main classes at the colon and consequently can't compile the test sources... Should I report this as a bug? -- Thank you and have fun, Siegmar
colon_issue.tar.bz2
Description: BZip2 compressed data
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
