[
https://issues.apache.org/jira/browse/MNG-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14501631#comment-14501631
]
Jeffry Gaston commented on MNG-5806:
------------------------------------
Also interesting is that if the parent pom, P, doesn't exist on disk at the
specified location, then Maven 3.3.2 looks in the Maven repository (whereas if
it exists in the specified location, then it tries to find it there but then
doesn't)
> Inconsistent resolution of parent.relativePath with symlinks
> ------------------------------------------------------------
>
> Key: MNG-5806
> URL: https://issues.apache.org/jira/browse/MNG-5806
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.3.1, 3.3.2
> Environment: Ubuntu
> Reporter: Jeffry Gaston
> Attachments: maven-relativePath-symlink-error.zip
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Suppose a reactor pom.xml, R, specifies that it has a child module, C.
> Suppose that C exists but not is actually located at some other, unrelated
> path to R (not one directory deeper than R).
> Suppose that the working directory for R contains a symlink, S (which looks
> like C), with the same name as C, pointing at the directory containing C.
> Suppose that C specifies a parent P and provides a relativePath at which to
> find P.
> Suppose that P exists at the specified relative path.
> Then, when a user `mvn clean install` while R is in the working directory,
> then Maven will state that P does not exist, and it will display the wrong
> path to P: the value it will list will be the value that could be computed
> using string manipulation based on the location of R, the name of C, and the
> relativePath to P, without first resolving the symlink that is C.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
