Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-6261

Relative parent POM resolution failing in 3.5.0 with complex multimodule builds

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.5.0
    • Fix Version/s: 3.6.1
    • Component/s: None
    • Labels:

      Description

      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:

      > 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).
      

      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).

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              rfscholte Robert Scholte
              Reporter:
              dweiss Dawid Weiss

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment