[ http://jira.codehaus.org/browse/MNG-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-4814: ----------------------------------- Attachment: MNG-4814.zip A demo project which exhibits the issue upon running {{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.7:aggregate package -X}}. Here, the javadoc plugin will cause dependency resolution for the entire reactor (before anyhing has been actually built) and resolves the {{producer}} artifact from the remote repo. When performing the {{package}} lifecycle next, the classpaths of {{consumer}} still use the {{producer}} artifact from the local repo instead from the now populated reactor. > [regression] Eary dependency resolution attempts for reactor projects prevent > their later resolution from the reactor > --------------------------------------------------------------------------------------------------------------------- > > Key: MNG-4814 > URL: http://jira.codehaus.org/browse/MNG-4814 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories > Affects Versions: 3.0-beta-3 > Reporter: Benjamin Bentmann > Attachments: MNG-4814.zip > > > If some code triggers dependency resolution for an artifact in the reactor > when that project artifact hasn't been built yet and the resolution reaches > out to a remote repo instead, any later resolution attempts will stick to the > artifact from the repo even if the reactor produced the artifact in the > meantime. -- 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