Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Apache Maven 3.0.4-RC3 (r1210461; 2011-12-05 14:58:54+0100)
Maven home: /usr/local/Cellar/maven/current/libexec
Java version: 1.6.0_29, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home
Default locale: de_DE, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"Apache Maven 3.0.4-RC3 (r1210461; 2011-12-05 14:58:54+0100) Maven home: /usr/local/Cellar/maven/current/libexec Java version: 1.6.0_29, vendor: Apple Inc. Java home: /Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home Default locale: de_DE, platform encoding: MacRoman OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
-
Patch
Description
With SVN the developerConnection and connection are
updated to the "real" release URL, that is when I invoke release:prepare with
a URL like:
https://SVNSERVER/svn/REPO/myproject/branches/release it will be
replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0
which is fine because now you know which revision to checkout for
building the release.
With git there is no such possibility to realize this with rewriting
the URL AFAIK. So I would have expected however, that maybe the //project/scm/tag
element would be updated to reflect the fact, that the pom is the one
of release, either to the "symbolic name" myproject-1.0 or to the hash
of the tag.
See http://markmail.org/thread/m77cvhqqq56krzzd as well.