You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2007/11/21 14:21:57 UTC
[jira] Created: (MNG-3297) maven should not give dependencies to
plugins that don't @requireDependencyResolution
maven should not give dependencies to plugins that don't @requireDependencyResolution
-------------------------------------------------------------------------------------
Key: MNG-3297
URL: http://jira.codehaus.org/browse/MNG-3297
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0.7
Reporter: Brian Fox
Currently we seem to hand over the dependencies as resolved by the last plugin. This leads to scenarios where sometimes plugins work because they get the right ones but it is subject to break at anytime in subtle ways. Therefore, we should give nothing to the plugin so the plugin author will realize the mistake immediately.
--
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
[jira] Closed: (MNG-3297) maven should not give dependencies to
plugins that don't @requireDependencyResolution
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-3297.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-alpha-7
Fixed in [r904309|http://svn.apache.org/viewvc?view=revision&revision=904309].
> maven should not give dependencies to plugins that don't @requireDependencyResolution
> -------------------------------------------------------------------------------------
>
> Key: MNG-3297
> URL: http://jira.codehaus.org/browse/MNG-3297
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.7
> Reporter: Brian Fox
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-7
>
>
> Currently we seem to hand over the dependencies as resolved by the last plugin. This leads to scenarios where sometimes plugins work because they get the right ones but it is subject to break at any time in subtle ways. Therefore, we should give nothing to the plugin so the plugin author will realize the mistake immediately.
--
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
[jira] Closed: (MNG-3297) maven should not give dependencies to
plugins that don't @requireDependencyResolution
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-3297.
------------------------------
Resolution: Incomplete
Fix Version/s: (was: 3.x)
> maven should not give dependencies to plugins that don't @requireDependencyResolution
> -------------------------------------------------------------------------------------
>
> Key: MNG-3297
> URL: http://jira.codehaus.org/browse/MNG-3297
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.7
> Reporter: Brian Fox
>
> Currently we seem to hand over the dependencies as resolved by the last plugin. This leads to scenarios where sometimes plugins work because they get the right ones but it is subject to break at any time in subtle ways. Therefore, we should give nothing to the plugin so the plugin author will realize the mistake immediately.
--
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
[jira] Updated: (MNG-3297) maven should not give dependencies to
plugins that don't @requireDependencyResolution
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MNG-3297:
---------------------------
Description: Currently we seem to hand over the dependencies as resolved by the last plugin. This leads to scenarios where sometimes plugins work because they get the right ones but it is subject to break at any time in subtle ways. Therefore, we should give nothing to the plugin so the plugin author will realize the mistake immediately. (was: Currently we seem to hand over the dependencies as resolved by the last plugin. This leads to scenarios where sometimes plugins work because they get the right ones but it is subject to break at anytime in subtle ways. Therefore, we should give nothing to the plugin so the plugin author will realize the mistake immediately.)
> maven should not give dependencies to plugins that don't @requireDependencyResolution
> -------------------------------------------------------------------------------------
>
> Key: MNG-3297
> URL: http://jira.codehaus.org/browse/MNG-3297
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.7
> Reporter: Brian Fox
>
> Currently we seem to hand over the dependencies as resolved by the last plugin. This leads to scenarios where sometimes plugins work because they get the right ones but it is subject to break at any time in subtle ways. Therefore, we should give nothing to the plugin so the plugin author will realize the mistake immediately.
--
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
[jira] Updated: (MNG-3297) maven should not give dependencies to
plugins that don't @requireDependencyResolution
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3297:
------------------------------
Fix Version/s: 2.1
> maven should not give dependencies to plugins that don't @requireDependencyResolution
> -------------------------------------------------------------------------------------
>
> Key: MNG-3297
> URL: http://jira.codehaus.org/browse/MNG-3297
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.7
> Reporter: Brian Fox
> Fix For: 2.1
>
>
> Currently we seem to hand over the dependencies as resolved by the last plugin. This leads to scenarios where sometimes plugins work because they get the right ones but it is subject to break at any time in subtle ways. Therefore, we should give nothing to the plugin so the plugin author will realize the mistake immediately.
--
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
[jira] Reopened: (MNG-3297) maven should not give dependencies to
plugins that don't @requireDependencyResolution
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann reopened MNG-3297:
------------------------------------
Assignee: Benjamin Bentmann
> maven should not give dependencies to plugins that don't @requireDependencyResolution
> -------------------------------------------------------------------------------------
>
> Key: MNG-3297
> URL: http://jira.codehaus.org/browse/MNG-3297
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.7
> Reporter: Brian Fox
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-7
>
>
> Currently we seem to hand over the dependencies as resolved by the last plugin. This leads to scenarios where sometimes plugins work because they get the right ones but it is subject to break at any time in subtle ways. Therefore, we should give nothing to the plugin so the plugin author will realize the mistake immediately.
--
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