You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2008/02/19 07:23:28 UTC
[jira] Created: (MNG-3410) Managed versions in plugins are not
considered when using them
Managed versions in plugins are not considered when using them
--------------------------------------------------------------
Key: MNG-3410
URL: http://jira.codehaus.org/browse/MNG-3410
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0.8, 2.1-alpha-1, 2.1
Reporter: Carlos Sanchez
If you build and install a plugin with managed versions that affect plugin transitive dependencies, when it's used the dependency management is ignored
If the dependency management affects the plugin direct dependecies it works properly because the information is merged.
eg.
Plugin A depends on jar B that depends on jar C[1.0]
A dependencyManagement explicitly forces C[2.0], you build and install using C[2.0] in the classpath
If you use plugin A in your pom it will be used with C version 1.0
--
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-3410) Managed versions in plugins are not
considered when using them
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3410:
------------------------------
Fix Version/s: (was: 2.1-alpha-1)
(was: 2.1)
> Managed versions in plugins are not considered when using them
> --------------------------------------------------------------
>
> Key: MNG-3410
> URL: http://jira.codehaus.org/browse/MNG-3410
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.8, 2.1-alpha-1, 2.1
> Reporter: Carlos Sanchez
> Assignee: Carlos Sanchez
> Fix For: 2.0.9
>
> Attachments: MNG-3410.patch
>
>
> If you build and install a plugin with managed versions that affect plugin transitive dependencies, when it's used the dependency management is ignored
> If the dependency management affects the plugin direct dependecies it works properly because the information is merged.
> eg.
> Plugin A depends on jar B that depends on jar C[1.0]
> A dependencyManagement explicitly forces C[2.0], you build and install using C[2.0] in the classpath
> If you use plugin A in your pom it will be used with C version 1.0
--
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-3410) Managed versions in plugins are not
considered when using them
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez closed MNG-3410.
-------------------------------
Assignee: Carlos Sanchez
Resolution: Fixed
Fix Version/s: 2.1
2.1-alpha-1
2.0.9
> Managed versions in plugins are not considered when using them
> --------------------------------------------------------------
>
> Key: MNG-3410
> URL: http://jira.codehaus.org/browse/MNG-3410
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.8, 2.1-alpha-1, 2.1
> Reporter: Carlos Sanchez
> Assignee: Carlos Sanchez
> Fix For: 2.0.9, 2.1-alpha-1, 2.1
>
> Attachments: MNG-3410.patch
>
>
> If you build and install a plugin with managed versions that affect plugin transitive dependencies, when it's used the dependency management is ignored
> If the dependency management affects the plugin direct dependecies it works properly because the information is merged.
> eg.
> Plugin A depends on jar B that depends on jar C[1.0]
> A dependencyManagement explicitly forces C[2.0], you build and install using C[2.0] in the classpath
> If you use plugin A in your pom it will be used with C version 1.0
--
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-3410) Managed versions in plugins are not
considered when using them
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated MNG-3410:
--------------------------------
Attachment: MNG-3410.patch
Tentative patch
> Managed versions in plugins are not considered when using them
> --------------------------------------------------------------
>
> Key: MNG-3410
> URL: http://jira.codehaus.org/browse/MNG-3410
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.8, 2.1-alpha-1, 2.1
> Reporter: Carlos Sanchez
> Attachments: MNG-3410.patch
>
>
> If you build and install a plugin with managed versions that affect plugin transitive dependencies, when it's used the dependency management is ignored
> If the dependency management affects the plugin direct dependecies it works properly because the information is merged.
> eg.
> Plugin A depends on jar B that depends on jar C[1.0]
> A dependencyManagement explicitly forces C[2.0], you build and install using C[2.0] in the classpath
> If you use plugin A in your pom it will be used with C version 1.0
--
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] Commented: (MNG-3410) Managed versions in plugins are not
considered when using them
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124260 ]
Carlos Sanchez commented on MNG-3410:
-------------------------------------
Added testcase along with test for MNG-3396 into core-integration-tests/src/test/resources/mng-3396-dependencyManagementForOverConstrainedRanges
> Managed versions in plugins are not considered when using them
> --------------------------------------------------------------
>
> Key: MNG-3410
> URL: http://jira.codehaus.org/browse/MNG-3410
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.8, 2.1-alpha-1, 2.1
> Reporter: Carlos Sanchez
>
> If you build and install a plugin with managed versions that affect plugin transitive dependencies, when it's used the dependency management is ignored
> If the dependency management affects the plugin direct dependecies it works properly because the information is merged.
> eg.
> Plugin A depends on jar B that depends on jar C[1.0]
> A dependencyManagement explicitly forces C[2.0], you build and install using C[2.0] in the classpath
> If you use plugin A in your pom it will be used with C version 1.0
--
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