Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.7
-
Fix Version/s: 2.0.8
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
We are running on Ubuntu and our environment is as follows:
./pom.xml (is a symbolic link to /baseline/pom.xml)
./module/pom.xml (is a symbolic link to /baseline/module/pom.xml)
If you go into the module directory and run a compile (mvn compile), everything works fine.
If you try to run a compile from the parent pom, maven does not resolve the basedir correctly when it tries to compile the module. It tries to create the target directory in /baseline/module/target, rather than in the local module directory.
Everything works as expected in release 2.0.6. Something changed with the symbolic link resolution in 2.0.7 that breaks my builds.
-Rob
Attachments
Issue Links
| This issue depends upon: | ||||
| MNG-2687 | Module paths may be too long on Windows |
|
|
|
I haven't been able to verify this, but from looking at the code, it looks like the following change:
revision 543362, Fri Jun 1 02:29:37 2007 UTC
on the file:
maven-2.0.x/maven-core/src/main/java/org/apache/maven/DefaultMaven.java
is causing the problem.