maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Oster (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-36) Release plugin fails to update SNAPSHOTS in the dependencyManagement section
Date Tue, 14 Jun 2011 21:11:42 GMT

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

Scott Oster commented on MRELEASE-36:
-------------------------------------

This appears to have regressed... can this be reopened and fixed in the 2.1 or 2.2 stream?

> Release plugin fails to update SNAPSHOTS in the dependencyManagement section
> ----------------------------------------------------------------------------
>
>                 Key: MRELEASE-36
>                 URL: http://jira.codehaus.org/browse/MRELEASE-36
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>         Environment: Maven 2.0 (release-plugin version: 2.0-beta3)
>            Reporter: Ørjan Austvold
>            Assignee: John Casey
>         Attachments: prep.txt
>
>
> In a multi project the parent-pom can specify "standard" versions for dependencies within
the project group. I have found it convenient to also list group-members with versions in
this section so that all child artifact within the group simply specifies inter-group artifact
dependencies without versions.
> The release plugin fails to alter SNAPSHOT dependencies within the dependencyMangement
section. The tagged version of child poms gets instead the correct version explicitly stated
in their dependency section.
> It seems a bit strange that dependencies on artifacts within a group must have dependencies
on other artifacts within the group listed with version numbers.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message