I thought about the same thing. Although m-release-p 2.5 hasn't proven
itself yet, it might be better to use it since a lot of Apache projects
already use Git.
There's a small justification: both version 2.3.2 and 2.4.2 use SCM 1.7,
so it won't get worse.
Robert
Op Thu, 06 Mar 2014 22:54:39 +0100 schreef Arnaud Héritier
<aherit...@gmail.com>:
Wasn't it necessary to upgrade to the release plugin 2.5 (even if it was
just published) to solve all Git related bugs for people using a version
>=
1.8.5 ?
Arnaud
On Thu, Mar 6, 2014 at 10:18 PM, Hervé BOUTEMY
<herve.bout...@free.fr>wrote:
Hi,
Changes since the last release:
http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEAD&r2=1434717&diff_format=h
Staging repo:
https://repository.apache.org/content/repositories/orgapacheapache-1000/
https://repository.apache.org/content/repositories/orgapacheapache-1000/org/apache/apache/14/apache-14-source-release.zip
Source release checksum:
apache-14-source-release.zip sha1:
6bed0856a4cc8d9ee5f4481b8a1e0a4460076073
Staging site:
http://maven.apache.org/pom-archives/asf-LATEST/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org