[ https://issues.apache.org/jira/browse/MNG-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690568#comment-16690568 ]
ASF GitHub Bot commented on MNG-6261: ------------------------------------- fabcipriano opened a new pull request #192: [MNG-6261] - using java File api to compare URL: https://github.com/apache/maven/pull/192 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MNG-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MNG-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 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 > Labels: up-for-grabs > Fix For: 3.6.x-candidate > > 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 (v7.6.3#76005)