[
https://issues.apache.org/jira/browse/MNG-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429277#comment-17429277
]
Eugene Evdokimov commented on MNG-5806:
---------------------------------------
This issue still remains in Maven 3.8.3
> 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
> Priority: Major
> Attachments: maven-relativePath-symlink-error.zip
>
> Original Estimate: 1h
> Time Spent: 10m
> Remaining Estimate: 50m
>
> 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
(v8.3.4#803005)
