Parent POM not created by reactor if not found in repository

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.0.3
  • Fix Version/s: 2.0.3
  • Component/s: Artifacts and Repositories
  • Labels:
    None
  • Complexity:
    Intermediate

Description

Consider a multi-module project with usual parent-child relationship

pom.xml
module-1/pom.xml
...
module-n/pom.xml

Executing install goal from top-level fails due to failure to find parent POM in any repository

Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository

<groupId>:<artifactId>:pom:<version>

Using maven-2.0.2 this does not occur and the parent POM is installed if not found - as expected.
Hence a regression.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
John Casey added a comment -

I believe this has to do with the fix for the multiple projectId problem...the building process doesn't check the project-cache for the parent project, therefore will miss parent projects that are cached from the current builds...

Show
John Casey added a comment - I believe this has to do with the fix for the multiple projectId problem...the building process doesn't check the project-cache for the parent project, therefore will miss parent projects that are cached from the current builds...
Hide
Permalink
John Casey added a comment -

see it0099

Show
John Casey added a comment - see it0099

People

  • Assignee:
    John Casey
    Reporter:
    Mauro Talevi
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: