[jira] Updated: (MRELEASE-454) The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import
[ http://jira.codehaus.org/browse/MRELEASE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Rodriguez updated MRELEASE-454: - Attachment: MRELEASE-454.patch This is the complete patch containing both changes and unit tests Please, ignore MRELEASE-454.diff The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import Key: MRELEASE-454 URL: http://jira.codehaus.org/browse/MRELEASE-454 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.0-beta-9 Reporter: Jens Mühlenhoff Attachments: MRELEASE-454.diff, MRELEASE-454.patch Add the following node to the pom. Then prepare the release and this section will not be rewriten, because the imported entry will not appear in project.getDependencyManagement().getDependencies(). This methode returns all the resolved dependencies. In this situation the transformDocument method from AbstractRewritePomsPhase could not change the given dependencies, because it is not visible to the method. dependencyManagement dependencies dependency groupIddist/groupId artifactIddeps/artifactId typepom/type version4.0.4-SNAPSHOT/version scopeimport/scope /dependency /dependencies /dependencyManagement -- 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: (MRELEASE-454) The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import
[ http://jira.codehaus.org/browse/MRELEASE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Rodriguez updated MRELEASE-454: - Attachment: MRELEASE-412_and_MRELEASE-454.patch This is the patch file to fix MRELEASE-412 and MRELEASE-454 Please, ignore the previous MRELEASE-454.path The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import Key: MRELEASE-454 URL: http://jira.codehaus.org/browse/MRELEASE-454 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.0-beta-9 Reporter: Jens Mühlenhoff Attachments: MRELEASE-412_and_MRELEASE-454.patch, MRELEASE-454.diff, MRELEASE-454.patch Add the following node to the pom. Then prepare the release and this section will not be rewriten, because the imported entry will not appear in project.getDependencyManagement().getDependencies(). This methode returns all the resolved dependencies. In this situation the transformDocument method from AbstractRewritePomsPhase could not change the given dependencies, because it is not visible to the method. dependencyManagement dependencies dependency groupIddist/groupId artifactIddeps/artifactId typepom/type version4.0.4-SNAPSHOT/version scopeimport/scope /dependency /dependencies /dependencyManagement -- 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: (MRELEASE-454) The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import
[ http://jira.codehaus.org/browse/MRELEASE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Rodriguez updated MRELEASE-454: - Attachment: MRELEASE-454.diff A diff file with the documented changes to fix this issue The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import Key: MRELEASE-454 URL: http://jira.codehaus.org/browse/MRELEASE-454 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.0-beta-9 Reporter: Jens Mühlenhoff Attachments: MRELEASE-454.diff Add the following node to the pom. Then prepare the release and this section will not be rewriten, because the imported entry will not appear in project.getDependencyManagement().getDependencies(). This methode returns all the resolved dependencies. In this situation the transformDocument method from AbstractRewritePomsPhase could not change the given dependencies, because it is not visible to the method. dependencyManagement dependencies dependency groupIddist/groupId artifactIddeps/artifactId typepom/type version4.0.4-SNAPSHOT/version scopeimport/scope /dependency /dependencies /dependencyManagement -- 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