[
http://jira.codehaus.org/browse/MNG-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MNG-2277.
--------------------------
Resolution: Fixed
Fix Version/s: (was: 2.1)
2.0.8
When a dependency can't be resolved AND the same is found in the reactor AND
the plugin is an aggregator, we produce a large warning and then skip it. A
clone of this issue has been created for possible further solution in 2.1:
MNG-3260
> aggregating plugins in submodules of the reactor return all projects causing
> a chicken/egg issue
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2277
> URL: http://jira.codehaus.org/browse/MNG-2277
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API, Plugins and Lifecycle, Reactor and workspace
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Assignee: Brian Fox
> Fix For: 2.0.8
>
>
> eg, assembly:attached
> when this is put in maven-core, and a build is run from the root project with
> a clean repo, it fails, as the original project sorter doesn't consider the
> dependencies, building plugin-tools after maven-core.
> However, hitting the aggregator when building maven-core then tries to
> resolve all of the projects as dependencies.
--
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
