Maven 2.x Release Plugin

release-pom.xml does not contain <dependencies> and <dependencyManagement>

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-6
  • Fix Version/s: 2.0-beta-7
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

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.

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-245 CheckDependencySnapshotsPhase ignores ranges

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-3023 Reactor projects should be included in dependency resolution

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-3 release:prepare should not require multimodule artifacts to be in the local repository

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Mark Hobson added a comment -

Yep, this is due to @requiresDependencyResolution being dropped from the MRELEASE-177 patch. See the following thread for an in-progress discussion on fixing this:

http://www.mail-archive.com/dev@maven.apache.org/msg67188.html

Show
Mark Hobson added a comment - Yep, this is due to @requiresDependencyResolution being dropped from the MRELEASE-177 patch. See the following thread for an in-progress discussion on fixing this: http://www.mail-archive.com/dev@maven.apache.org/msg67188.html
Hide
Permalink
Mark Hobson added a comment -

Attached patch adds @rDR back into release:prepare to fix the missing dependencies problem, as agreed over IRC with Brett and summarised in the above thread. The dependencyManagement block is never present in a release pom since dependencies are fully resolved.

Show
Mark Hobson added a comment - Attached patch adds @rDR back into release:prepare to fix the missing dependencies problem, as agreed over IRC with Brett and summarised in the above thread. The dependencyManagement block is never present in a release pom since dependencies are fully resolved.
Hide
Permalink
Mark Hobson added a comment -

Patch applied.

Show
Mark Hobson added a comment - Patch applied.
Hide
Permalink
Brett Porter added a comment -

Note that we intend to revert this change and make it possible in a different way for 2.0: http://mail-archives.apache.org/mod_mbox/maven-dev/201001.mbox/%3C4B56E5A7.9050806@udo.edu%3E

Show
Brett Porter added a comment - Note that we intend to revert this change and make it possible in a different way for 2.0: http://mail-archives.apache.org/mod_mbox/maven-dev/201001.mbox/%3C4B56E5A7.9050806@udo.edu%3E
Hide
Permalink
hanasaki added a comment -

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.

Show
hanasaki added a comment - 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.

People

  • Assignee:
    Mark Hobson
    Reporter:
    Yann Le Du
Vote (3)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: