[
http://jira.codehaus.org/browse/MNG-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Mohn updated MNG-3141:
-----------------------------
Attachment: DefaultMaven.java.patch
Patch for the issue. The patch checks if the file is a symlink before doing
the getCanonicalFile conversion. The 'isSymLink' method was taken from
CleanMojo.java -- so at some point we should move that method into a utility
class.
> Build not working if pom.xml is a symbolic link
> -----------------------------------------------
>
> Key: MNG-3141
> URL: http://jira.codehaus.org/browse/MNG-3141
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.7
> Reporter: Robert Mohn
> Attachments: DefaultMaven.java.patch
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
