[
http://jira.codehaus.org/browse/MRELEASE-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212353#action_212353
]
hanasaki commented on MRELEASE-240:
-----------------------------------
Running maven 2.2.1 on Ubuntu 9.10 (tried with both the maven download and the
Ubuntu package of mvn)
Just built and deployed a snapshot (project1) with dependencyManagement and
used it with a pom import in another project's (project2) pom.xml
dependencyManagement OK
Released to a repository and the released non-SNAPSHOT version does not have
dependencyManagement section. project2 updated to to use the released project1
fails because there are no versions in its dependencies (expecting them from
the import)
Reproduced via command line and Husdon CI
Tried alpha6 of 3.0 mvn however this fails with the Hudson plugin and the cmd
line cannot be tried at this time.
> release-pom.xml does not contain <dependencies> and <dependencyManagement>
> --------------------------------------------------------------------------
>
> Key: MRELEASE-240
> URL: http://jira.codehaus.org/browse/MRELEASE-240
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-6
> Reporter: Yann Le Du
> Assignee: Mark Hobson
> Fix For: 2.0-beta-7
>
> Attachments: MRELEASE-240.patch
>
>
> Since version 2.0-beta-6, mvn release:prepare -DgenerateReleasePoms=true
> creates release-pom.xml, which is good.
> Though, this release-pom.xml does not contain the <dependencies> and
> <dependencyManagement> sections of the original POM.
--
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
