[jira] Closed: (MNG-3141) Build not working if pom.xml is a symbolic link

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MNG-3141.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.8

I wasn't able to apply your patch, since AFAICT that would simply revert the previous issue (on Windows, it would not canonicalize either do to the check).

Instead, I used an Os.isFamily check to only canonicalize on Windows.

> 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
>            Assignee: Brett Porter
>             Fix For: 2.0.8
>
>         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