Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.7
-
None
-
None
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
Attachments
Issue Links
- depends upon
-
MNG-2687 Module paths may be too long on Windows
- Closed