[ https://issues.apache.org/jira/browse/MNG-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104877#comment-16104877 ]
Dawid Weiss commented on MNG-6261: ---------------------------------- One more comment - to get the 'different' drive letter on windows you have to sweat a bit (use {{/d}} switch to enforce full path change): {code} # switch to c drive (or a different drive) > c: # switch to lowercase d drive: > cd /d d:\ # switch to uppercase D drive: > cd /d D:\ {code} > Relative parent POM resolution failing in 3.5.0 with complex multimodule > builds > ------------------------------------------------------------------------------- > > Key: MNG-6261 > URL: https://issues.apache.org/jira/browse/MNG-6261 > Project: Maven > Issue Type: Bug > Affects Versions: 3.5.0 > Reporter: Dawid Weiss > Priority: Minor > Attachments: capture-6.png, repro.zip > > > In my effort to upgrade an existing (fairly complex) Maven build to Java > 1.9.0 I updated Maven to 3.5.0 (from 3.3.9). Unfortunately I get errors when > the project's modules are resolved: > {noformat} > > mvn validate > [FATAL] Non-resolvable parent POM for > com.carrotsearch.lingo4g:lingo4g-public-bom:[unknown-version]: Could not find > artifact com.carrotsearch.lingo4g:lingo4g-public:pom:1.6.0-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 5, column 11 > ... > (and many follow). > {noformat} > This build has a correct pom parent-structure (a tree), but is fairly complex > -- the submodule hierarchy is not aligned with parent-child pom hierarchy > (it's best to look at the repro code to understand how it's structured). > However, it's been working correctly with all prior Maven versions and I > wonder if it's a regression bug or maybe underspecified Maven requirement > (that should be enforced with a warning and not lead to this odd runtime > message). -- This message was sent by Atlassian JIRA (v6.4.14#64029)