[ 
https://jira.codehaus.org/browse/MRELEASE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323442#comment-323442
 ] 

Torsten Liermann commented on MRELEASE-454:
-------------------------------------------

Please reopen the bug for release plugin version 2.4 and maven 3.0.4

Maven-release-plugin:prepare does not update the version of the imported 
dependency management. 

Thanks
Torsten
                
> The Release-Plugin does not rewrite dependencies in the DependencyManagement 
> with scope "import"
> ------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-454
>                 URL: https://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
>            Assignee: Benjamin Bentmann
>             Fix For: 2.2.2
>
>         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>
>                               <groupId>dist</groupId>
>                               <artifactId>deps</artifactId>
>                               <type>pom</type>
>                               <version>4.0.4-SNAPSHOT</version>
>                               <scope>import</scope>
>                       </dependency>
>               </dependencies>
> </dependencyManagement>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to