You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/03/29 00:40:25 UTC
[jira] Closed: (MNG-1949) project-level plugin dependencies not
handled correctly in multimodule builds
[ http://jira.codehaus.org/browse/MNG-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-1949.
----------------------------------
Resolution: Duplicate
Fix Version/s: (was: 3.0-alpha-8)
Assignee: Benjamin Bentmann
> project-level plugin dependencies not handled correctly in multimodule builds
> -----------------------------------------------------------------------------
>
> Key: MNG-1949
> URL: http://jira.codehaus.org/browse/MNG-1949
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.1
> Reporter: John Casey
> Assignee: Benjamin Bentmann
>
> plugin containers are only initialized once per build, which means they may contain incorrect project-introduced dependencies for project Y in a multimodule build (polluted by project X predecessor). We should look at ways of dumping plugin containers with project-specific configurations, or else providing a container overlay to handle project-specific dependencies, etc.
> NOTE: This is tied into the notions of build extensions, which will have similar consequences on the core container.
--
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