[ http://jira.codehaus.org/browse/MNG-2130?page=comments#action_60397 ]
John Casey commented on MNG-2130: --------------------------------- 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... > Parent POM not created by reactor if not found in repository > ------------------------------------------------------------ > > Key: MNG-2130 > URL: http://jira.codehaus.org/browse/MNG-2130 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.3 > Reporter: Mauro Talevi > Assignee: John Casey > Priority: Blocker > > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
