maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Updated] (MNG-5806) Inconsistent resolution of parent.relativePath with symlinks
Date Fri, 28 Dec 2018 23:12:00 GMT


Michael Osipov updated MNG-5806:
    Fix Version/s: waiting-for-feedback

> Inconsistent resolution of parent.relativePath with symlinks
> ------------------------------------------------------------
>                 Key: MNG-5806
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.3.1, 3.3.2
>         Environment: Ubuntu
>            Reporter: Jeffry Gaston
>            Priority: Major
>             Fix For: waiting-for-feedback
>         Attachments:
>   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

This message was sent by Atlassian JIRA

View raw message