Hi,
On 5/6/16 6:32 PM, Stian Soiland-Reyes wrote:
OK, that's inverse process from other ASF projects I've been on -
which require a commit ID in the email because of the fact you CAN
change a tag AND drop a Staging repository; e.g. it is not a
long-lasting record of the vote (for the failed RCs at least).
The record of the VOTE or CANCELED VOTE's is done via the mailing
list...Yes of course i can remove a tag and drop a staging
repository...yes exactly that's the purpose of such staging repository
to check the quality of such artifacts..if it does not fit the
requirements than i can simply forget about it instead of synched into
central...and in SVN the remove of a tag is recorded...in contradiction
to Git where removing a tag is not recorded in anyway...
Perhaps that is a bit paranoid :-) But it somewhat guards against
anyone doing a "manual" release by accident.
The release process is manual work at the moment...How does it do that?
Who will prevent me from doing a release if already a tag exists ? Only
the maven-release-plugin will fail, based on the existing tag in SVN/Tag
which is more safe than using a different Tag Name than the final one...
Kind regards
Karl Heinz
I thing Commons has a mechanism to add the git/SVN revision id into
the META-INF/MANIFEST.MF of the JAR in the Maven repository - which is
quite nice.
Yes i know that it is possible... might be a good idea to add those
informations in the MANIFEST.MF (buildnumber-maven-plugin plugin ..)...
On 6 May 2016 at 16:59, Karl Heinz Marbaise <[email protected]> wrote:
Hi Stian,
On 5/6/16 5:39 PM, Stian Soiland-Reyes wrote:
The commit id was missing from the vote email.
We don't use the commit id in the vote mails cause we only stage the release
which has a related tag in svn:
svn log -v -l1
https://svn.apache.org/repos/asf/maven/plugins/tags/maven-jar-plugin-3.0.0
I assume you mean:
https://svn.apache.org/repos/asf/maven/plugins/tags/maven-jar-plugin-3.0.0/@1742311
(I would have expected the tag to be maven-jar-plugin-3.0.0-RC1 until
the release vote was passed)
We don't produce RC's cause if a failure is in there we drop the release
from the staging repository and reuse the version number...and remove svn
tag...and we will never change a TAG after a successfull vote...
You have used the wrong revision:
If you take a look here:
~/apache-maven/maven-plugins$ svn log -v -l5
https://svn.apache.org/repos/asf/maven/plugins/tags/
------------------------------------------------------------------------
r1742485 | khmarbaise | 2016-05-06 00:35:17 +0200 (Fri, 06 May 2016) | 1
line
Changed paths:
A /maven/plugins/tags/maven-resources-plugin-3.0.0 (from
/maven/plugins/trunk/maven-resources-plugin:1742484)
[maven-release-plugin] copy for tag maven-resources-plugin-3.0.0
------------------------------------------------------------------------
r1742311 | khmarbaise | 2016-05-04 20:01:36 +0200 (Wed, 04 May 2016) | 1
line
Changed paths:
A /maven/plugins/tags/maven-jar-plugin-3.0.0 (from
/maven/plugins/trunk/maven-jar-plugin:1742310)
[maven-release-plugin] copy for tag maven-jar-plugin-3.0.0
------------------------------------------------------------------------
r1741751 | khmarbaise | 2016-04-30 13:32:17 +0200 (Sat, 30 Apr 2016) | 1
line
Changed paths:
D /maven/plugins/tags/maven-jar-plugin-3.0.0
Removed based on CANCELED VOTE
------------------------------------------------------------------------
r1740872 | khmarbaise | 2016-04-25 20:16:44 +0200 (Mon, 25 Apr 2016) | 1
line
Changed paths:
A /maven/plugins/tags/maven-jar-plugin-3.0.0 (from
/maven/plugins/trunk/maven-jar-plugin:1740871)
[maven-release-plugin] copy for tag maven-jar-plugin-3.0.0
I verified the above match against
maven-jar-plugin-3.0.0-source-release.zip sha1:
b749bfd9e76b92102f372fd807b17779c4d03c7e
stain@biggie:/var/tmp/maven-jar-plugin-3.0.0$ svn status
? DEPENDENCIES
? LICENSE
? NOTICE
! src/it/MJAR-162/src/test/java/.gitignore
! src/it/MJAR-162/src/test/resources/.gitignore
What are you trying ? you can't run svn status on a release-source.zip cause
does not contain SVN information...
Thanks for so much verifying...appreciated...
Kind regards
Karl Heinz Marbaise
On 4 May 2016 at 19:16, Karl Heinz Marbaise <[email protected]> wrote:
Hi,
We solved 21 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12334171
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-1265
https://repository.apache.org/content/repositories/maven-1265/org/apache/maven/plugins/maven-jar-plugin/3.0.0/maven-jar-plugin-3.0.0-source-release.zip
Source release checksum(s):
maven-jar-plugin-3.0.0-source-release.zip sha1:
b749bfd9e76b92102f372fd807b17779c4d03c7e
Staging site:
http://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise USt.IdNr: DE191347579
Hauptstrasse 177
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
