Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20 - TAKE 3

[Andreas Gudian]

+1

Tested on a couple of projects, with Maven 3.3.9 and 3.5.0, on Win
(binaries) and macOS (source build).

Great job, Tibor!


2017-04-08 14:26 GMT+02:00 Petr Široký :

> +1 (non-binding)
>
> Tested on Fedora 25 + JDK 8u121 + Maven 3.5.0 with several large projects.
> No issue found.
>
> @Tibor, thanks for fixing all the issues I found previously!
>
> Petr
>
> On Sat, Apr 8, 2017 at 12:53 PM Tibor Digana 
> wrote:
>
> > Hi,
> >
> > We solved 70 issues:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317927=12334636
> >
> > There are still a couple of issues left in JIRA:
> >
> > https://issues.apache.org/jira/i#issues/?jql=project+%
> 3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1330/
> >
> > https://repository.apache.org/content/repositories/maven-
> 1330/org/apache/maven/surefire/surefire/2.20/surefire-2.20-source-release.
> zip
> >
> > Source release checksum(s):
> > surefire-2.20-source-release.zip sha1:
> > fda994228c52dcb581d8ce6d4664f84a29d78797
> >
> > Git tag:
> >
> > https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=
> 8c786523414018099b54a0868ae1bc3d64847411
> >
> > Staging site:
> > http://maven.apache.org/surefire-archives/surefire-LATEST/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Cheers,
> > Tibor
> >
>

Re: No helping on the 3.5.0 release checklist...

[Stephen Connolly]

All done now: https://maven.apache.org/docs/history.html has the announce
link for 3.5.0

P A R T Y !!!

On 7 April 2017 at 22:05, Stephen Connolly 
wrote:

> 24. Publish the website with https://cms.apache.org/maven/publish
> 25. Send the announcement email
> 26. (PMC only) Record the release on https://reporter.apache.
> org/addrelease.html?maven
> 27. Tweet the release
>
> TODO:
> 28. Wait for the announcement email to show up on the
> https://mail-archives.apache.org/mod_mbox/maven-announce/ archives
> 29. Update the site history with the announce email
> 30. Publish the site again
> 31. Celebrate!!!
>
> On 7 April 2017 at 09:59, Stephen Connolly  com> wrote:
>
>> 23. Mark the version in JIRA as released
>>
>> On 7 April 2017 at 09:40, Stephen Connolly > om> wrote:
>>
>>> 14. Close the vote
>>> 15. Commit the finalized release notes
>>> 16. Commit the updated doap
>>> 17. Add the release to the dist
>>>
>>> $ cd ~/tmp
>>> $ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3 maven-dist
>>> $ cd maven-dist
>>> $ mkdir -p 3.5.0/{binaries,source}
>>> $ for ext in tar.gz zip ; do ( cd 3.5.0/binaries/ ; for hash in "" .asc
>>> .md5 .sha1 ; do curl -O https://repository.apache.org/
>>> content/repositories/maven-1326/org/apache/maven/apache-mave
>>> n/3.5.0/apache-maven-3.5.0-bin.$ext$hash ; done ) done
>>> $ for ext in tar.gz zip ; do ( cd 3.5.0/source/ ; for hash in "" .asc
>>> .md5 .sha1 ; do curl -O https://repository.apache.org/
>>> content/repositories/maven-1326/org/apache/maven/apache-mave
>>> n/3.5.0/apache-maven-3.5.0-src.$ext$hash ; done ) done
>>> $ svn add 3.5.0
>>> $ svn ci -m "Staging the binaries for the release"
>>>
>>> 18. Release the staging repo in nexus
>>> 19. Release the binaries
>>>
>>> $ svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.0
>>> https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Release
>>> 3.5.0"
>>>
>>> 20. Deploy the current reference
>>>
>>> $ svn cp https://svn.apache.org/repos/infra/websites/production/maven
>>> /components/ref/3-LATEST https://svn.apache.org/repos/i
>>> nfra/websites/production/maven/components/ref/3.5.0 -m "Deploy the
>>> 3.5.0 reference documentation"
>>>
>>> 21. Draft the Announcement email
>>>
>>> 22. Wait for the binaries to sync to the mirrors (check
>>> https://www.apache.org/mirrors/ look at the mean / median mirror age,
>>> wait that long)
>>>
>>> On 4 April 2017 at 07:40, Stephen Connolly <
>>> stephen.alan.conno...@gmail.com> wrote:
>>>
 12. Run the integration tests: (in debian as that matches the ci server)

 $ ID=$(docker build environments/debian-jdk7) &&
 docker run -it --rm -v $(pwd):/root/maven-integration-testing -v
 $(pwd)/../maven:/root/maven $ID bash
 $ cd /root
 $ mvn clean install -Prun-its -Dmaven.repo.local=$HOME/tmp/repo
 -DmavenDistro=../maven/target/checkout/apache-maven/target/a
 pache-maven-3.5.0-bin.zip

 13. Publish the integration tests site: (by bind mounting the test run
 we can publish the results from inside docker outside of docker)

 $ mvn -Preporting site site:stage && mvn scm-publish:publish-scm

 On 3 April 2017 at 23:36, Stephen Connolly <
 stephen.alan.conno...@gmail.com> wrote:

> 11. Run the source release analyzer (https://github.com/stephenc/s
> ource-release-validator/commit/2e91ac959d0320a509e023b11b638
> 9cc05719cdb) and reply to the vote with the results.
>
> On 3 April 2017 at 23:18, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> Note to self, here's all the steps so far
>>
>> 1. $ export JAVA_HOME=jdk7
>> 2. $ export PATH=${JAVA_HOME}/bin:${PATH}
>> 3. $ mvn release:prepare release:perform
>> 4. $ cd target/checkout
>> 5. $ export MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=512m
>> 6. Close staging repo
>> 7. $ mvn -Preporting site site:stage
>> 8. $ mvn scm-publish:publish-scm
>> 9. Send vote email
>> 10. Start preparing the release notes
>>
>
>

>>>
>>
>

Re: [ANN] Apache Maven 3.5.0 Released

[Gary Gregory]

+1

Gary

On Apr 8, 2017 4:13 AM, "sebb"  wrote:

> What is the project about? Why should I be interested in it?
> [rhetorical questions]
>
> The Announce emails are sent to people not on the developer or user lists.
> Many will have no idea what the project is about.
>
> So the e-mails should contain at least brief details of what the
> product does, and some info on why the new release might be of
> interest to them.
>
> Readers should not have to click the link to find out the basic information
> (although of course it is useful to have such links for further detail).
>
> Please can you add that information to future announce mails?
>
> Thanks.
>
> I realise that Maven is a lot better known than some other ASF
> projects, however that does not mean it is universally known.
>
> HTTPD, Tomcat and Ant all include a summary of their project in Announce
> mails.
>
> On 7 April 2017 at 22:07, Stephen Connolly  wrote:
> > The Apache Maven team would like to announce the release of Apache Maven
> > 3.5.0.
> >
> > You can download the appropriate sources etc. from the download page
> >
> > http://maven.apache.org/download.cgi
> >
> > Notable changes
> > ===
> >
> > - ANSI colors added to the console output
> > - Fix various bugs in mvn scripts regarding spaces, quotations, special
> > characters, etc. also in combination with .mvn/ -files
> > - Switch from Eclipse Aether to Maven Artifact Resolver
> >
> > What happened to Maven 3.4.0?
> > =
> >
> > After Maven 3.3.9 was released, the Eclipse Aether project was retired
> and
> > the code base was migrated to the Apache Maven project.
> >
> > The original goal for the 3.4.0 release was to replace Aether with the
> > exact same code after migration to the Apache Maven project and then
> > proceed with bug fixes to the resolver code as well as other areas of
> Maven.
> >
> > The migration of the code between the two foundations took longer than
> > expected and as a result there were other changes committed to Maven core
> > that were outside the scope of intent for 3.4.0.
> >
> > In order to refocus on the original intent for 3.4.0, the decision was
> > taken to revert the Maven core history to the point of the 3.3.9 release
> > and merge in the desired changes one at a time.
> >
> > Because there had been a lot of communication about different features
> > being delivered and bugs fixed in Maven 3.4.0 and the new history may not
> > contain them in the first release, the decision was taken to forever burn
> > the 3.4.x release line.
> >
> > More detail on this decision can be read in the mailing list archive[1].
> >
> > Contributors
> > 
> >
> > The Apache Maven team would like to thank the following contributors,
> > without whom this release would not have been possible:
> >
> > Code contributors:
> >
> > - Alex Henrie
> > - Andriy
> > - Archimedes Trajano
> > - Arlo Louis O'Keeffe
> > - August Shi
> > - Christoph Böhme
> > - Harald Wellmann
> > - Jason Dillon
> > - Joseph Walton
> > - Josh Soref
> > - Miriam Lee
> > - Nemo Chen
> > - Sébastian Le Merdy
> > - Stuart McCulloch
> > - Tobias Oberlies
> > - Robert Patrick
> >
> > Issue reporters:
> >
> > - Alex Henrie
> > - Andreas Sewe
> > - Andrew Haines
> > - Andriy
> > - Anthony Whitford
> > - Archimedes Trajano
> > - August Shi
> > - Ben Caradoc-Davies
> > - Christoph Böhme
> > - Daniel Spilker
> > - Falko Modler
> > - Fred Bricon
> > - Harald Wellmann
> > - Jeffrey Alexander
> > - Josh Soref
> > - Kengo TODA
> > - Konrad Windszus
> > - Laird Nelson
> > - Larry Singer
> > - Meytal Genah
> > - Mike Drob
> > - Miriam Lee
> > - Nemo Chen
> > - Peter Kjær Guldbæk
> > - Rahul Thakur
> > - Richard Raumberger
> > - Stuart McCulloch
> > - Tobias Oberlies
> > - Zac Thompson
> >
> > Community testers participating in voting for this release series:
> >
> > -  Grzegorz Grzybek
> > -  Petr Široký
> > -  Mark Derricutt,
> > -  Dejan Stojadinović
> > -  Thomas Collignon
> > -  Fred Cooke
> > -  Raphael Ackermann
> > -  Elliot Metsger
> > -  Chas Honton
> > -  Dennis Kieselhorst
> >
> > The Apache Maven Project Management Committee would also like to thank
> all
> > the committers to the project for their efforts during the chaos that was
> > the great reset when the 3.4.x release lines were burned.
> >
> > Release Notes - Maven - Version 3.5.0
> > =
> >
> > Bugs:
> >
> > * [MNG-5297] - Site should tell 'prerequisites.maven is deprecated'
> > * [MNG-5368] - UnsupportedOperationException thrown when version
> range
> > is not correct in dependencyManagement definitions
> > * [MNG-5629] - ClosedChannelException from
> > DefaultUpdateCheckManager.read
> > * [MNG-5815] - "mvn.cmd" does not indicate failure properly when
> using
> > "&&"
> > * [MNG-5823] - mvnDebug doesn't work with M2_HOME with spaces -
> missing
> > quotes
> > * [MNG-5829] - mvn shell script fails with syntax 

Release Apache Maven Archetype Plugin version 3.0.1

[Robert Scholte]

Hi,

We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122=12339582=Text

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317122%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1331
https://repository.apache.org/content/repositories/maven-1331/org/apache/maven/archetype/maven-archetype/3.0.1/maven-archetype-3.0.1-source-release.zip

Source release checksum(s):
maven-archetype-3.0.1-source-release.zip sha1:  
7332a5f891eb8ec128afa068ed669a9fa4420533


Staging site:
https://maven.apache.org/archetype-archives/archetype-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20 - TAKE 3

[Petr Široký]

+1 (non-binding)

Tested on Fedora 25 + JDK 8u121 + Maven 3.5.0 with several large projects.
No issue found.

@Tibor, thanks for fixing all the issues I found previously!

Petr

On Sat, Apr 8, 2017 at 12:53 PM Tibor Digana  wrote:

> Hi,
>
> We solved 70 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12334636
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1330/
>
> https://repository.apache.org/content/repositories/maven-1330/org/apache/maven/surefire/surefire/2.20/surefire-2.20-source-release.zip
>
> Source release checksum(s):
> surefire-2.20-source-release.zip sha1:
> fda994228c52dcb581d8ce6d4664f84a29d78797
>
> Git tag:
>
> https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=8c786523414018099b54a0868ae1bc3d64847411
>
> Staging site:
> http://maven.apache.org/surefire-archives/surefire-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Cheers,
> Tibor
>

Re: No helping on the 3.5.0 release checklist...

[Stephen Connolly]

Perhaps

On Sat 8 Apr 2017 at 13:22, Robert Scholte  wrote:

> Time to think of a release:finalize?
>
> On Fri, 07 Apr 2017 23:13:08 +0200, Stephen Connolly
>  wrote:
>
> > On 7 April 2017 at 22:10, Fred Cooke  wrote:
> >
> >> Thanks for all of your hard work on this, much appreciated!
> >>
> >> A little feedback for 3.5.1 (not helping with 3.5.0): checksums for the
> >> binaries too, not just the source.
> >>
> >>
> > checksums are in the staging repo and on the dowload site too. legally we
> > only vote on the source distribution. we can look into providing the
> > checksums as a convenience but 30 steps is too much for a release... I
> > want
> > to strip that way way down
> >
> >
> >> That's it. :-)
> >>
> >> On 8 April 2017 at 09:05, Stephen Connolly  >> com>
> >> wrote:
> >>
> >> > 24. Publish the website with https://cms.apache.org/maven/publish
> >> > 25. Send the announcement email
> >> > 26. (PMC only) Record the release on
> >> > https://reporter.apache.org/addrelease.html?maven
> >> > 27. Tweet the release
> >> >
> >> > TODO:
> >> > 28. Wait for the announcement email to show up on the
> >> > https://mail-archives.apache.org/mod_mbox/maven-announce/ archives
> >> > 29. Update the site history with the announce email
> >> > 30. Publish the site again
> >> > 31. Celebrate!!!
> >> >
> >> > On 7 April 2017 at 09:59, Stephen Connolly
> >>  >> > com>
> >> > wrote:
> >> >
> >> > > 23. Mark the version in JIRA as released
> >> > >
> >> > > On 7 April 2017 at 09:40, Stephen Connolly
> >>  >> > > com> wrote:
> >> > >
> >> > >> 14. Close the vote
> >> > >> 15. Commit the finalized release notes
> >> > >> 16. Commit the updated doap
> >> > >> 17. Add the release to the dist
> >> > >>
> >> > >> $ cd ~/tmp
> >> > >> $ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3
> >> > maven-dist
> >> > >> $ cd maven-dist
> >> > >> $ mkdir -p 3.5.0/{binaries,source}
> >> > >> $ for ext in tar.gz zip ; do ( cd 3.5.0/binaries/ ; for hash in ""
> >> .asc
> >> > >> .md5 .sha1 ; do curl -O https://repository.apache.org/
> >> > >> content/repositories/maven-1326/org/apache/maven/apache-mave
> >> > >> n/3.5.0/apache-maven-3.5.0-bin.$ext$hash ; done ) done
> >> > >> $ for ext in tar.gz zip ; do ( cd 3.5.0/source/ ; for hash in ""
> >> .asc
> >> > >> .md5 .sha1 ; do curl -O https://repository.apache.org/
> >> > >> content/repositories/maven-1326/org/apache/maven/apache-mave
> >> > >> n/3.5.0/apache-maven-3.5.0-src.$ext$hash ; done ) done
> >> > >> $ svn add 3.5.0
> >> > >> $ svn ci -m "Staging the binaries for the release"
> >> > >>
> >> > >> 18. Release the staging repo in nexus
> >> > >> 19. Release the binaries
> >> > >>
> >> > >> $ svn mv
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.0
> >> > >> https://dist.apache.org/repos/dist/release/maven/maven-3 -m
> >> "Release
> >> > >> 3.5.0"
> >> > >>
> >> > >> 20. Deploy the current reference
> >> > >>
> >> > >> $ svn cp
> >> https://svn.apache.org/repos/infra/websites/production/maven
> >> > >> /components/ref/3-LATEST https://svn.apache.org/repos/i
> >> > >> nfra/websites/production/maven/components/ref/3.5.0 -m "Deploy the
> >> > 3.5.0
> >> > >> reference documentation"
> >> > >>
> >> > >> 21. Draft the Announcement email
> >> > >>
> >> > >> 22. Wait for the binaries to sync to the mirrors (check
> >> > >> https://www.apache.org/mirrors/ look at the mean / median mirror
> >> age,
> >> > >> wait that long)
> >> > >>
> >> > >> On 4 April 2017 at 07:40, Stephen Connolly
> >> >  >> > >> om> wrote:
> >> > >>
> >> > >>> 12. Run the integration tests: (in debian as that matches the ci
> >> > server)
> >> > >>>
> >> > >>> $ ID=$(docker build environments/debian-jdk7) &&
> >> > >>> docker run -it --rm -v $(pwd):/root/maven-integration-testing -v
> >> > >>> $(pwd)/../maven:/root/maven $ID bash
> >> > >>> $ cd /root
> >> > >>> $ mvn clean install -Prun-its -Dmaven.repo.local=$HOME/tmp/repo
> >> > >>> -DmavenDistro=../maven/target/checkout/apache-maven/target/a
> >> > >>> pache-maven-3.5.0-bin.zip
> >> > >>>
> >> > >>> 13. Publish the integration tests site: (by bind mounting the test
> >> run
> >> > >>> we can publish the results from inside docker outside of docker)
> >> > >>>
> >> > >>> $ mvn -Preporting site site:stage && mvn scm-publish:publish-scm
> >> > >>>
> >> > >>> On 3 April 2017 at 23:36, Stephen Connolly <
> >> > >>> stephen.alan.conno...@gmail.com> wrote:
> >> > >>>
> >> >  11. Run the source release analyzer
> >> (https://github.com/stephenc/s
> >> >  ource-release-validator/commit/2e91ac959d0320a509e023b11b6389
> >> > cc05719cdb)
> >> >  and reply to the vote with the results.
> >> > 
> >> >  On 3 April 2017 at 23:18, Stephen Connolly <
> >> >  stephen.alan.conno...@gmail.com> wrote:
> >> > 
> >> > > Note to self, here's 

Re: No helping on the 3.5.0 release checklist...

[Robert Scholte]

Time to think of a release:finalize?

On Fri, 07 Apr 2017 23:13:08 +0200, Stephen Connolly  
 wrote:



On 7 April 2017 at 22:10, Fred Cooke  wrote:


Thanks for all of your hard work on this, much appreciated!

A little feedback for 3.5.1 (not helping with 3.5.0): checksums for the
binaries too, not just the source.



checksums are in the staging repo and on the dowload site too. legally we
only vote on the source distribution. we can look into providing the
checksums as a convenience but 30 steps is too much for a release... I  
want

to strip that way way down



That's it. :-)

On 8 April 2017 at 09:05, Stephen Connolly 
wrote:

> 24. Publish the website with https://cms.apache.org/maven/publish
> 25. Send the announcement email
> 26. (PMC only) Record the release on
> https://reporter.apache.org/addrelease.html?maven
> 27. Tweet the release
>
> TODO:
> 28. Wait for the announcement email to show up on the
> https://mail-archives.apache.org/mod_mbox/maven-announce/ archives
> 29. Update the site history with the announce email
> 30. Publish the site again
> 31. Celebrate!!!
>
> On 7 April 2017 at 09:59, Stephen Connolly  
 com>
> wrote:
>
> > 23. Mark the version in JIRA as released
> >
> > On 7 April 2017 at 09:40, Stephen Connolly
 > com> wrote:
> >
> >> 14. Close the vote
> >> 15. Commit the finalized release notes
> >> 16. Commit the updated doap
> >> 17. Add the release to the dist
> >>
> >> $ cd ~/tmp
> >> $ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3
> maven-dist
> >> $ cd maven-dist
> >> $ mkdir -p 3.5.0/{binaries,source}
> >> $ for ext in tar.gz zip ; do ( cd 3.5.0/binaries/ ; for hash in ""
.asc
> >> .md5 .sha1 ; do curl -O https://repository.apache.org/
> >> content/repositories/maven-1326/org/apache/maven/apache-mave
> >> n/3.5.0/apache-maven-3.5.0-bin.$ext$hash ; done ) done
> >> $ for ext in tar.gz zip ; do ( cd 3.5.0/source/ ; for hash in ""  
.asc

> >> .md5 .sha1 ; do curl -O https://repository.apache.org/
> >> content/repositories/maven-1326/org/apache/maven/apache-mave
> >> n/3.5.0/apache-maven-3.5.0-src.$ext$hash ; done ) done
> >> $ svn add 3.5.0
> >> $ svn ci -m "Staging the binaries for the release"
> >>
> >> 18. Release the staging repo in nexus
> >> 19. Release the binaries
> >>
> >> $ svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.0
> >> https://dist.apache.org/repos/dist/release/maven/maven-3 -m  
"Release

> >> 3.5.0"
> >>
> >> 20. Deploy the current reference
> >>
> >> $ svn cp  
https://svn.apache.org/repos/infra/websites/production/maven

> >> /components/ref/3-LATEST https://svn.apache.org/repos/i
> >> nfra/websites/production/maven/components/ref/3.5.0 -m "Deploy the
> 3.5.0
> >> reference documentation"
> >>
> >> 21. Draft the Announcement email
> >>
> >> 22. Wait for the binaries to sync to the mirrors (check
> >> https://www.apache.org/mirrors/ look at the mean / median mirror  
age,

> >> wait that long)
> >>
> >> On 4 April 2017 at 07:40, Stephen Connolly
>  >> om> wrote:
> >>
> >>> 12. Run the integration tests: (in debian as that matches the ci
> server)
> >>>
> >>> $ ID=$(docker build environments/debian-jdk7) &&
> >>> docker run -it --rm -v $(pwd):/root/maven-integration-testing -v
> >>> $(pwd)/../maven:/root/maven $ID bash
> >>> $ cd /root
> >>> $ mvn clean install -Prun-its -Dmaven.repo.local=$HOME/tmp/repo
> >>> -DmavenDistro=../maven/target/checkout/apache-maven/target/a
> >>> pache-maven-3.5.0-bin.zip
> >>>
> >>> 13. Publish the integration tests site: (by bind mounting the test
run
> >>> we can publish the results from inside docker outside of docker)
> >>>
> >>> $ mvn -Preporting site site:stage && mvn scm-publish:publish-scm
> >>>
> >>> On 3 April 2017 at 23:36, Stephen Connolly <
> >>> stephen.alan.conno...@gmail.com> wrote:
> >>>
>  11. Run the source release analyzer  
(https://github.com/stephenc/s

>  ource-release-validator/commit/2e91ac959d0320a509e023b11b6389
> cc05719cdb)
>  and reply to the vote with the results.
> 
>  On 3 April 2017 at 23:18, Stephen Connolly <
>  stephen.alan.conno...@gmail.com> wrote:
> 
> > Note to self, here's all the steps so far
> >
> > 1. $ export JAVA_HOME=jdk7
> > 2. $ export PATH=${JAVA_HOME}/bin:${PATH}
> > 3. $ mvn release:prepare release:perform
> > 4. $ cd target/checkout
> > 5. $ export MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=512m
> > 6. Close staging repo
> > 7. $ mvn -Preporting site site:stage
> > 8. $ mvn scm-publish:publish-scm
> > 9. Send vote email
> > 10. Start preparing the release notes
> >
> 
> 
> >>>
> >>
> >
>


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [ANN] Apache Maven 3.5.0 Released

[sebb]

What is the project about? Why should I be interested in it?
[rhetorical questions]

The Announce emails are sent to people not on the developer or user lists.
Many will have no idea what the project is about.

So the e-mails should contain at least brief details of what the
product does, and some info on why the new release might be of
interest to them.

Readers should not have to click the link to find out the basic information
(although of course it is useful to have such links for further detail).

Please can you add that information to future announce mails?

Thanks.

I realise that Maven is a lot better known than some other ASF
projects, however that does not mean it is universally known.

HTTPD, Tomcat and Ant all include a summary of their project in Announce mails.

On 7 April 2017 at 22:07, Stephen Connolly  wrote:
> The Apache Maven team would like to announce the release of Apache Maven
> 3.5.0.
>
> You can download the appropriate sources etc. from the download page
>
> http://maven.apache.org/download.cgi
>
> Notable changes
> ===
>
> - ANSI colors added to the console output
> - Fix various bugs in mvn scripts regarding spaces, quotations, special
> characters, etc. also in combination with .mvn/ -files
> - Switch from Eclipse Aether to Maven Artifact Resolver
>
> What happened to Maven 3.4.0?
> =
>
> After Maven 3.3.9 was released, the Eclipse Aether project was retired and
> the code base was migrated to the Apache Maven project.
>
> The original goal for the 3.4.0 release was to replace Aether with the
> exact same code after migration to the Apache Maven project and then
> proceed with bug fixes to the resolver code as well as other areas of Maven.
>
> The migration of the code between the two foundations took longer than
> expected and as a result there were other changes committed to Maven core
> that were outside the scope of intent for 3.4.0.
>
> In order to refocus on the original intent for 3.4.0, the decision was
> taken to revert the Maven core history to the point of the 3.3.9 release
> and merge in the desired changes one at a time.
>
> Because there had been a lot of communication about different features
> being delivered and bugs fixed in Maven 3.4.0 and the new history may not
> contain them in the first release, the decision was taken to forever burn
> the 3.4.x release line.
>
> More detail on this decision can be read in the mailing list archive[1].
>
> Contributors
> 
>
> The Apache Maven team would like to thank the following contributors,
> without whom this release would not have been possible:
>
> Code contributors:
>
> - Alex Henrie
> - Andriy
> - Archimedes Trajano
> - Arlo Louis O'Keeffe
> - August Shi
> - Christoph Böhme
> - Harald Wellmann
> - Jason Dillon
> - Joseph Walton
> - Josh Soref
> - Miriam Lee
> - Nemo Chen
> - Sébastian Le Merdy
> - Stuart McCulloch
> - Tobias Oberlies
> - Robert Patrick
>
> Issue reporters:
>
> - Alex Henrie
> - Andreas Sewe
> - Andrew Haines
> - Andriy
> - Anthony Whitford
> - Archimedes Trajano
> - August Shi
> - Ben Caradoc-Davies
> - Christoph Böhme
> - Daniel Spilker
> - Falko Modler
> - Fred Bricon
> - Harald Wellmann
> - Jeffrey Alexander
> - Josh Soref
> - Kengo TODA
> - Konrad Windszus
> - Laird Nelson
> - Larry Singer
> - Meytal Genah
> - Mike Drob
> - Miriam Lee
> - Nemo Chen
> - Peter Kjær Guldbæk
> - Rahul Thakur
> - Richard Raumberger
> - Stuart McCulloch
> - Tobias Oberlies
> - Zac Thompson
>
> Community testers participating in voting for this release series:
>
> -  Grzegorz Grzybek
> -  Petr Široký
> -  Mark Derricutt,
> -  Dejan Stojadinović
> -  Thomas Collignon
> -  Fred Cooke
> -  Raphael Ackermann
> -  Elliot Metsger
> -  Chas Honton
> -  Dennis Kieselhorst
>
> The Apache Maven Project Management Committee would also like to thank all
> the committers to the project for their efforts during the chaos that was
> the great reset when the 3.4.x release lines were burned.
>
> Release Notes - Maven - Version 3.5.0
> =
>
> Bugs:
>
> * [MNG-5297] - Site should tell 'prerequisites.maven is deprecated'
> * [MNG-5368] - UnsupportedOperationException thrown when version range
> is not correct in dependencyManagement definitions
> * [MNG-5629] - ClosedChannelException from
> DefaultUpdateCheckManager.read
> * [MNG-5815] - "mvn.cmd" does not indicate failure properly when using
> "&&"
> * [MNG-5823] - mvnDebug doesn't work with M2_HOME with spaces - missing
> quotes
> * [MNG-5829] - mvn shell script fails with syntax error on Solaris 10
> * [MNG-5836] - logging config is overridden by $M2_HOME/lib/ext/*.jar
> * [MNG-5852] - mvn shell script invokes /bin/sh but requires Bash
> functions
> * [MNG-5895] - Problem with CI friendly usage of ${..} which is already
> defined via property in pom file.
> * [MNG-5958] - java.lang.String cannot be cast to
> 

[VOTE] Release Apache Maven Surefire Plugin version 2.20 - TAKE 3

[Tibor Digana]

Hi,

We solved 70 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12334636

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1330/
https://repository.apache.org/content/repositories/maven-1330/org/apache/maven/surefire/surefire/2.20/surefire-2.20-source-release.zip

Source release checksum(s):
surefire-2.20-source-release.zip sha1:
fda994228c52dcb581d8ce6d4664f84a29d78797

Git tag:
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=8c786523414018099b54a0868ae1bc3d64847411

Staging site:
http://maven.apache.org/surefire-archives/surefire-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Cheers,
Tibor

[CANCELLED] [VOTE] Release Apache Maven Surefire Plugin version 2.20 - TAKE 2

[Tibor Digana]

I am cancelling the second vote due to debugging issue.
I will start new Vote in a while.

[GitHub] maven pull request #106: Fixing a typo in 'lifecycle'

[hmemcpy]

Github user hmemcpy closed the pull request at:

https://github.com/apache/maven/pull/106


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20 - TAKE 2

[Hervé BOUTEMY]

FTR, SNAPSHOTs do not get to central
they go to Apache SNAPSHOT repository:
https://repository.apache.org/content/groups/snapshots/

Regards,

Hervé

Le samedi 8 avril 2017, 00:27:55 CEST Tibor Digana a écrit :
> The CI build will finish after 3 hours.
> Then the SNAPSHOT version will be in Maven Central.
> 
> On Fri, Apr 7, 2017 at 11:40 PM, Dan Tran  wrote:
> > is 2.20-SNAPSHOT up to date? that is only quick way I can test
> > 
> > Thanks
> > 
> > -D
> > 
> > On Fri, Apr 7, 2017 at 2:03 PM, Tibor Digana 
> > 
> > wrote:
> > > @Petr
> > > Both issues are fixed now. Would you please verify this version from
> > > master? I tested on my side.
> > > 
> > > On Fri, Apr 7, 2017 at 3:42 PM, Petr Široký 
> > 
> > wrote:
> > > > I'try to take a look. However, I have no prior experience with jUnit
> > > > or
> > > > surefire sources, so it might take a while until I have something.
> > > > 
> > > > Thanks,
> > > > Petr
> > > > 
> > > > On Fri, Apr 7, 2017 at 2:22 PM Tibor Digana <
> > 
> > tibor.dig...@googlemail.com
> > 
> > > > wrote:
> > > > > Good point. The PING chcking should be disabled when JMX observes
> > 
> > debug
> > 
> > > > > mode.
> > > > > See implementation in JUnit sources. The same is there.
> > > > > Can you open pull request with a fix?
> > > > > 
> > > > > On Fri, Apr 7, 2017 at 11:06 AM, Petr Široký 
> > > > > 
> > > > > wrote:
> > > > > > Hello,
> > > > > > 
> > > > > > thanks for the fast turnaround.
> > > > > > 
> > > > > > I am afraid I've hit another issue (or maybe misconfiguration?). I
> > > 
> > > was
> > > 
> > > > > > trying to use -Dmaven.surefire.debug in the following project:
> > > > > > https://github.com/psiroky/surefire-2.20-debug-reproducer
> > > > > > 
> > > > > > $ mvn clean install -s settings.xml -Dmaven.surefire.debug
> > > > > > 
> > > > > > The surefire stops the execution and waits for the remote
> > 
> > connection
> > 
> > > on
> > > 
> > > > > the
> > > > > 
> > > > > > default port 5005. However, I see this warning:
> > > > > > [WARNING] Corrupted stdin stream in forked JVM 2. See the dump
> > > > > > file
> > > > > > /home/psiroky/tmp/surefire-2.20-debug/target/surefire-
> > > > > > reports/2017-04-07T11-00-40_341-jvmRun2.dumpstream
> > > > > > 
> > > > > > Also, once I disconnect the remote debugger, the build fails with
> > > > > > "ExecutionException The forked VM terminated without properly
> > 
> > saying
> > 
> > > > > > goodbye. VM crash or System.exit called?"
> > > > > > See the full build.log in the above git repo. I've also included
> > 
> > the
> > 
> > > > > > '.dumpstream' file.
> > > > > > 
> > > > > > Petr
> > > > > > 
> > > > > > 
> > > > > > On Thu, Apr 6, 2017 at 7:56 AM Tibor Digana <
> > 
> > tibordig...@apache.org>
> > 
> > > > > > wrote:
> > > > > > > Hi,
> > > > > > > 
> > > > > > > We solved 68 issues:
> > > > > > > 
> > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > > 
> > > > > > projectId=12317927=12334636
> > > > > > 
> > > > > > > There are still a couple of issues left in JIRA:
> > > > > > > 
> > > > > > > https://issues.apache.org/jira/i#issues/?jql=project+%
> > > > > > 
> > > > > > 3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
> > > > > > 
> > > > > > > Staging repo:
> > > > > > > https://repository.apache.org/content/repositories/maven-1329/
> > > > > > > 
> > > > > > > https://repository.apache.org/content/repositories/maven-> > > > 
> > > > > > > > 
> > > > > 1329/org/apache/maven/surefire/surefire/2.20/
> > > > 
> > > > surefire-2.20-source-release.
> > > > 
> > > > > > zip
> > > > > > 
> > > > > > > Source release checksum(s):
> > > > > > > surefire-2.20-source-release.zip sha1:
> > > > > > > d76d172588f6ab1ada16db9155b464ffeefffc9b
> > > > > 
> > > > > > > Git tag:
> > > > > https://git-wip-us.apache.org/repos/asf?p=maven-surefire.
> > > 
> > > git;a=commit;h=
> > > 
> > > > > > b5cbc6b2822e9eb60c703d46f1d2ed82126909ed
> > > > > > 
> > > > > > > Staging site:
> > > > > > > http://maven.apache.org/surefire-archives/surefire-LATEST/
> > > > > > > 
> > > > > > > Guide to testing staged releases:
> > > > > > > http://maven.apache.org/guides/development/guide-> > > > 
> > > > testing-releases.html
> > > > 
> > > > > > > Vote open for 72 hours.
> > > > > > > 
> > > > > > > [ ] +1
> > > > > > > [ ] +0
> > > > > > > [ ] -1
> > > > > > > 
> > > > > > > Cheers,
> > > > > > > Tibor
> > > > > 
> > > > > --
> > > > > Cheers
> > > > > Tibor
> > > 
> > > --
> > > Cheers
> > > Tibor



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven issue #106: Fixing a typo in 'lifecycle'

[khmarbaise]

Github user khmarbaise commented on the issue:

https://github.com/apache/maven/pull/106
  
Can you please close that pull request.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20 - TAKE 2

[Tibor Digana]

Thx Petr, I will cancel this Vote and start another one soon.

On Sat, Apr 8, 2017 at 9:14 AM, Petr Široký  wrote:

> Just tested with local build from f4f78c9f155 (2.20-SNAPSHOT). Several
> large projects, no additional issue found.
>
> Petr
>
> On Sat, Apr 8, 2017 at 12:28 AM Tibor Digana 
> wrote:
>
> > The CI build will finish after 3 hours.
> > Then the SNAPSHOT version will be in Maven Central.
> >
> > On Fri, Apr 7, 2017 at 11:40 PM, Dan Tran  wrote:
> >
> > > is 2.20-SNAPSHOT up to date? that is only quick way I can test
> > >
> > > Thanks
> > >
> > > -D
> > >
> > > On Fri, Apr 7, 2017 at 2:03 PM, Tibor Digana <
> > tibor.dig...@googlemail.com>
> > > wrote:
> > >
> > > > @Petr
> > > > Both issues are fixed now. Would you please verify this version from
> > > > master? I tested on my side.
> > > >
> > > > On Fri, Apr 7, 2017 at 3:42 PM, Petr Široký 
> > > wrote:
> > > >
> > > > > I'try to take a look. However, I have no prior experience with
> jUnit
> > or
> > > > > surefire sources, so it might take a while until I have something.
> > > > >
> > > > > Thanks,
> > > > > Petr
> > > > >
> > > > > On Fri, Apr 7, 2017 at 2:22 PM Tibor Digana <
> > > tibor.dig...@googlemail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Good point. The PING chcking should be disabled when JMX observes
> > > debug
> > > > > > mode.
> > > > > > See implementation in JUnit sources. The same is there.
> > > > > > Can you open pull request with a fix?
> > > > > >
> > > > > > On Fri, Apr 7, 2017 at 11:06 AM, Petr Široký <
> > siroky.p...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > thanks for the fast turnaround.
> > > > > > >
> > > > > > > I am afraid I've hit another issue (or maybe
> misconfiguration?).
> > I
> > > > was
> > > > > > > trying to use -Dmaven.surefire.debug in the following project:
> > > > > > > https://github.com/psiroky/surefire-2.20-debug-reproducer
> > > > > > >
> > > > > > > $ mvn clean install -s settings.xml -Dmaven.surefire.debug
> > > > > > >
> > > > > > > The surefire stops the execution and waits for the remote
> > > connection
> > > > on
> > > > > > the
> > > > > > > default port 5005. However, I see this warning:
> > > > > > > [WARNING] Corrupted stdin stream in forked JVM 2. See the dump
> > file
> > > > > > > /home/psiroky/tmp/surefire-2.20-debug/target/surefire-
> > > > > > > reports/2017-04-07T11-00-40_341-jvmRun2.dumpstream
> > > > > > >
> > > > > > > Also, once I disconnect the remote debugger, the build fails
> with
> > > > > > > "ExecutionException The forked VM terminated without properly
> > > saying
> > > > > > > goodbye. VM crash or System.exit called?"
> > > > > > > See the full build.log in the above git repo. I've also
> included
> > > the
> > > > > > > '.dumpstream' file.
> > > > > > >
> > > > > > > Petr
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Apr 6, 2017 at 7:56 AM Tibor Digana <
> > > tibordig...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > We solved 68 issues:
> > > > > > > >
> > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > > > projectId=12317927=12334636
> > > > > > > >
> > > > > > > > There are still a couple of issues left in JIRA:
> > > > > > > >
> > > > > > > > https://issues.apache.org/jira/i#issues/?jql=project+%
> > > > > > > 3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
> > > > > > > >
> > > > > > > > Staging repo:
> > > > > > > > https://repository.apache.org/content/repositories/maven-
> 1329/
> > > > > > > >
> > > > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > > >
> > > > > > 1329/org/apache/maven/surefire/surefire/2.20/
> > > > > surefire-2.20-source-release.
> > > > > > > zip
> > > > > > > >
> > > > > > > > Source release checksum(s):
> > > > > > > > surefire-2.20-source-release.zip sha1:
> > > > > > > > d76d172588f6ab1ada16db9155b464ffeefffc9b
> > > > > > > >
> > > > > > > > Git tag:
> > > > > > > >
> > > > > > > >
> > > > > > https://git-wip-us.apache.org/repos/asf?p=maven-surefire.
> > > > git;a=commit;h=
> > > > > > > b5cbc6b2822e9eb60c703d46f1d2ed82126909ed
> > > > > > > >
> > > > > > > > Staging site:
> > > > > > > > http://maven.apache.org/surefire-archives/surefire-LATEST/
> > > > > > > >
> > > > > > > > Guide to testing staged releases:
> > > > > > > > http://maven.apache.org/guides/development/guide-
> > > > > testing-releases.html
> > > > > > > >
> > > > > > > > Vote open for 72 hours.
> > > > > > > >
> > > > > > > > [ ] +1
> > > > > > > > [ ] +0
> > > > > > > > [ ] -1
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Tibor
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Cheers
> > > > > > Tibor
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Cheers
> > > > Tibor
> > > >
> > >
> >
> >
> >
> > --
> > Cheers
> 

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.20 - TAKE 2

[Petr Široký]

Just tested with local build from f4f78c9f155 (2.20-SNAPSHOT). Several
large projects, no additional issue found.

Petr

On Sat, Apr 8, 2017 at 12:28 AM Tibor Digana 
wrote:

> The CI build will finish after 3 hours.
> Then the SNAPSHOT version will be in Maven Central.
>
> On Fri, Apr 7, 2017 at 11:40 PM, Dan Tran  wrote:
>
> > is 2.20-SNAPSHOT up to date? that is only quick way I can test
> >
> > Thanks
> >
> > -D
> >
> > On Fri, Apr 7, 2017 at 2:03 PM, Tibor Digana <
> tibor.dig...@googlemail.com>
> > wrote:
> >
> > > @Petr
> > > Both issues are fixed now. Would you please verify this version from
> > > master? I tested on my side.
> > >
> > > On Fri, Apr 7, 2017 at 3:42 PM, Petr Široký 
> > wrote:
> > >
> > > > I'try to take a look. However, I have no prior experience with jUnit
> or
> > > > surefire sources, so it might take a while until I have something.
> > > >
> > > > Thanks,
> > > > Petr
> > > >
> > > > On Fri, Apr 7, 2017 at 2:22 PM Tibor Digana <
> > tibor.dig...@googlemail.com
> > > >
> > > > wrote:
> > > >
> > > > > Good point. The PING chcking should be disabled when JMX observes
> > debug
> > > > > mode.
> > > > > See implementation in JUnit sources. The same is there.
> > > > > Can you open pull request with a fix?
> > > > >
> > > > > On Fri, Apr 7, 2017 at 11:06 AM, Petr Široký <
> siroky.p...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hello,
> > > > > >
> > > > > > thanks for the fast turnaround.
> > > > > >
> > > > > > I am afraid I've hit another issue (or maybe misconfiguration?).
> I
> > > was
> > > > > > trying to use -Dmaven.surefire.debug in the following project:
> > > > > > https://github.com/psiroky/surefire-2.20-debug-reproducer
> > > > > >
> > > > > > $ mvn clean install -s settings.xml -Dmaven.surefire.debug
> > > > > >
> > > > > > The surefire stops the execution and waits for the remote
> > connection
> > > on
> > > > > the
> > > > > > default port 5005. However, I see this warning:
> > > > > > [WARNING] Corrupted stdin stream in forked JVM 2. See the dump
> file
> > > > > > /home/psiroky/tmp/surefire-2.20-debug/target/surefire-
> > > > > > reports/2017-04-07T11-00-40_341-jvmRun2.dumpstream
> > > > > >
> > > > > > Also, once I disconnect the remote debugger, the build fails with
> > > > > > "ExecutionException The forked VM terminated without properly
> > saying
> > > > > > goodbye. VM crash or System.exit called?"
> > > > > > See the full build.log in the above git repo. I've also included
> > the
> > > > > > '.dumpstream' file.
> > > > > >
> > > > > > Petr
> > > > > >
> > > > > >
> > > > > > On Thu, Apr 6, 2017 at 7:56 AM Tibor Digana <
> > tibordig...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > We solved 68 issues:
> > > > > > >
> > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > > projectId=12317927=12334636
> > > > > > >
> > > > > > > There are still a couple of issues left in JIRA:
> > > > > > >
> > > > > > > https://issues.apache.org/jira/i#issues/?jql=project+%
> > > > > > 3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
> > > > > > >
> > > > > > > Staging repo:
> > > > > > > https://repository.apache.org/content/repositories/maven-1329/
> > > > > > >
> > > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > >
> > > > > 1329/org/apache/maven/surefire/surefire/2.20/
> > > > surefire-2.20-source-release.
> > > > > > zip
> > > > > > >
> > > > > > > Source release checksum(s):
> > > > > > > surefire-2.20-source-release.zip sha1:
> > > > > > > d76d172588f6ab1ada16db9155b464ffeefffc9b
> > > > > > >
> > > > > > > Git tag:
> > > > > > >
> > > > > > >
> > > > > https://git-wip-us.apache.org/repos/asf?p=maven-surefire.
> > > git;a=commit;h=
> > > > > > b5cbc6b2822e9eb60c703d46f1d2ed82126909ed
> > > > > > >
> > > > > > > Staging site:
> > > > > > > http://maven.apache.org/surefire-archives/surefire-LATEST/
> > > > > > >
> > > > > > > Guide to testing staged releases:
> > > > > > > http://maven.apache.org/guides/development/guide-
> > > > testing-releases.html
> > > > > > >
> > > > > > > Vote open for 72 hours.
> > > > > > >
> > > > > > > [ ] +1
> > > > > > > [ ] +0
> > > > > > > [ ] -1
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Tibor
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Cheers
> > > > > Tibor
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Cheers
> > > Tibor
> > >
> >
>
>
>
> --
> Cheers
> Tibor
>