[
https://issues.apache.org/jira/browse/MNG-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730495#comment-16730495
]
Michael Osipov commented on MNG-5806:
-------------------------------------
This test does not pass for me:
{noformat}
[mosipov@mika-ion ~/Projekte/maven-relativePath-symlink-error]$ ./test.sh
This test passes with Maven 3.0.5 and fails in Maven 3.3.2
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: /usr/local/share/java/maven3
Java version: 1.8.0_192, vendor: Oracle Corporation
Java home: /usr/local/openjdk8/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "11.2-release-p7", arch: "i386", family: "unix"
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.vecna.sample:grandchild:1-SNAPSHOT
(/usr/home/mosipov/Projekte/maven-relativePath-symlink-error/child2/grandchild/greatgrandchild/pom.xml)
has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact
com.vecna.sample:uncle:pom:1-SNAPSHOT and 'parent.relativePath' points at wrong
local POM @ line 10, column 11 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
[mosipov@mika-ion ~/Projekte/maven-relativePath-symlink-error]$
{noformat}
for
{noformat}
[mosipov@mika-ion ~/Projekte/maven-relativePath-symlink-error]$ tree -lpug
.
├── [drwxr-xr-x mosipov mosipov ] child1
│ └── [drwxr-xr-x mosipov mosipov ] grandchild
│ └── [-rw-r--r-- mosipov mosipov ] pom.xml
├── [drwxr-xr-x mosipov mosipov ] child2
│ ├── [drwxr-xr-x mosipov mosipov ] grandchild
│ │ ├── [lrwxr-xr-x mosipov mosipov ] greatgrandchild ->
/home/mosipov/Projekte/maven-relativePath-symlink-error/child1/grandchild
[recursive, not followed]
│ │ └── [-rw-r--r-- mosipov mosipov ] pom.xml
│ └── [-rw-r--r-- mosipov mosipov ] pom.xml
├── [-rwxr-xr-x mosipov mosipov ] test.sh
└── [drwxr-xr-x mosipov mosipov ] uncle
└── [-rw-r--r-- mosipov mosipov ] pom.xml
6 directories, 5 files
{noformat}
> 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
> Fix For: waiting-for-feedback
>
> 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
(v7.6.3#76005)
