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 2009/02/14 14:53:19 UTC
[jira] Updated: (MNG-3217) a plugin's dependencies can influence
other plugins in a build
[ http://jira.codehaus.org/browse/MNG-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-3217:
-----------------------------------
Fix Version/s: 2.1.0
Fixed in [r591391|http://svn.eu.apache.org/viewvc?view=rev&revision=591391] and [r744497|http://svn.eu.apache.org/viewvc?view=rev&revision=744497], respectively.
> a plugin's dependencies can influence other plugins in a build
> --------------------------------------------------------------
>
> Key: MNG-3217
> URL: http://jira.codehaus.org/browse/MNG-3217
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.7
> Reporter: Brian Fox
> Assignee: Benjamin Bentmann
> Fix For: 2.1.0, 3.0-alpha-1
>
>
> See the linked issue for more details.
> In short, the dependency plugin has declared a dependency on the site plugin (forget for now that this is probably not a good ide). The problem is that in doing this, the site plugin used for other things in the user's build is now pinned to the version declared in the dependency plugin. This seems to indicate some kind of pollution between what a plugin needs and what gets used for a build.
--
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