date:20170407

Re: [ANN] Apache Maven 3.5.0 Released

2017-04-07 Thread Gary Gregory

Thank you for the new release!

Gary

On Apr 7, 2017 2:07 PM, "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
> org.apache.maven.lifecycle.mapping.LifecyclePhase
> * [MNG-5961] - Maven possibly not aware of log4j2
> * [MNG-5962] - mvn.cmd fails when the current directory has spaces in
> between
> * [MNG-5963] - mvn.cmd does not return ERROR_CODE
> * [MNG-6022] - mvn.cmd fails if directory contains an ampersand (&)
> * [MNG-6053] - Unsafe System Properties copy in
> MavenRepositorySystemUtils, causing NPEs
> * [MNG-6057] - Problem with CI friendly usage of ${..} reactor order is
> changed
> * [MNG-6090] - CI friendly properties break submodule builds
> * [MNG-6105] - properties.internal.SystemProperties.
> addSystemProperties()
> is not really thread-safe
> * [MNG-6109] - PluginDescriptor doesn't read since value of parameter
> *

Re: [ANN] Apache Maven 3.5.0 Released

2017-04-07 Thread Chas Honton

Congratulations on a successful release!  Thanks to all of the maven core team 
for your work, particularly for the willingness to abandon 3.4 and reset to a 
more iterative approach. 

Thanks,
Chas

> On Apr 7, 2017, at 2:07 PM, 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
> org.apache.maven.lifecycle.mapping.LifecyclePhase
>* [MNG-5961] - Maven possibly not aware of log4j2
>* [MNG-5962] - mvn.cmd fails when the current directory has spaces in
> between
>* [MNG-5963] - mvn.cmd does not return ERROR_CODE
>* [MNG-6022] - mvn.cmd fails if directory contains an ampersand (&)
>* [MNG-6053] - Unsafe System Properties copy in
> MavenRepositorySystemUtils, causing NPEs
>* [MNG-6057] - Problem with CI friendly usage of ${..} reactor order is
> changed
>* [MNG-6090] - CI friendly properties break submodule builds
>* [MNG-6105] -

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

2017-04-07 Thread Tibor Digana

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
> >
>



-- 
Cheers
Tibor

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

2017-04-07 Thread Dan Tran

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  >
> > 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 
> > > > 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
>

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

2017-04-07 Thread Fred Cooke

Yes, agreed, 30 is a lot, but if you have N artifacts in a dir running
sha1sum dir/* and pasting the result raw into the email is not difficult.
Less so than formatting the two, probably.

On 8 April 2017 at 09:13, 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 all the steps so far
> > > >
> > > > 1. $ export JAVA_HOME=jdk7
> > > > 2. $ export

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

2017-04-07 Thread Stephen Connolly

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 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: No helping on the 3.5.0 release checklist...

2017-04-07 Thread Fred Cooke

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.

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
> >
> 
> 
> >>>
> >>
> >
>

[ANN] Apache Maven 3.5.0 Released

2017-04-07 Thread Stephen Connolly

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
org.apache.maven.lifecycle.mapping.LifecyclePhase
* [MNG-5961] - Maven possibly not aware of log4j2
* [MNG-5962] - mvn.cmd fails when the current directory has spaces in
between
* [MNG-5963] - mvn.cmd does not return ERROR_CODE
* [MNG-6022] - mvn.cmd fails if directory contains an ampersand (&)
* [MNG-6053] - Unsafe System Properties copy in
MavenRepositorySystemUtils, causing NPEs
* [MNG-6057] - Problem with CI friendly usage of ${..} reactor order is
changed
* [MNG-6090] - CI friendly properties break submodule builds
* [MNG-6105] - properties.internal.SystemProperties.addSystemProperties()
is not really thread-safe
* [MNG-6109] - PluginDescriptor doesn't read since value of parameter
* [MNG-6117] - ${session.parallel} not correctly set
* [MNG-6144] - DefaultWagonManagerTest#testGetMissingJarForced() passed
incorrect value
* [MNG-6166] - mvn dependency:go-offline fails due to missing
transitive dependency jdom:jdom:jar:1.1
* [MNG-6168] - Fix unclosed streams
* [MNG-6170] - NPE in cases using Multithreaded -T X versions:set
-DnewVersion=1.0-SNAPSHOT
*

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

2017-04-07 Thread Stephen Connolly

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 
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/2e91ac959d0320a509e023b11b6389cc05719cdb)
 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: [VOTE] Release Apache Maven Surefire Plugin version 2.20 - TAKE 2

2017-04-07 Thread Tibor Digana

@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 
> 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 
> > > 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

Re: is 3.5.1 open for business?

2017-04-07 Thread Igor Fedorenko

I completely agree we need to prove each code change does not break
existing integration tests (and I did run the tests locally with my
changes, fwiw)

-- 
Regards,
Igor

On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:
> I want every issue that changes code (not docs or javadocs) to have an
> integration test run before merging.
> 
> We were trying to get consensus on a process but the debate died without
> a
> conclusion
> 
> On Fri 7 Apr 2017 at 16:21, Igor Fedorenko  wrote:
> 
> > I have two of small-ish fixes I'd like to submit, so I was wondering if
> > master is open for 3.5.1 changes already or we want to give it little
> > more time in case we need to release any emergency patches.
> >
> > Also, what is the general bug fixing protocol now, push to directly to
> > master and be prepared to revert or always go through a
> > pull-request-review process? I don't mind going the code review route,
> > but in this particular case both changes touch 1-2 lines of code not
> > counting regression test code, so I am not sure how much value formal
> > code review process will provide.
> >
> > Also, does anyone know how to get my JIRA account fixed so I can
> > assign/close/etc bugs?
> >
> > Thank you in advance.
> >
> >
> > https://issues.apache.org/jira/browse/MNG-6210
> > https://issues.apache.org/jira/browse/MNG-6209
> >
> > --
> > Regards,
> > Igor
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> > --
> Sent from my phone

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

Re: is 3.5.1 open for business?

2017-04-07 Thread Stephen Connolly

I want every issue that changes code (not docs or javadocs) to have an
integration test run before merging.

We were trying to get consensus on a process but the debate died without a
conclusion

On Fri 7 Apr 2017 at 16:21, Igor Fedorenko  wrote:

> I have two of small-ish fixes I'd like to submit, so I was wondering if
> master is open for 3.5.1 changes already or we want to give it little
> more time in case we need to release any emergency patches.
>
> Also, what is the general bug fixing protocol now, push to directly to
> master and be prepared to revert or always go through a
> pull-request-review process? I don't mind going the code review route,
> but in this particular case both changes touch 1-2 lines of code not
> counting regression test code, so I am not sure how much value formal
> code review process will provide.
>
> Also, does anyone know how to get my JIRA account fixed so I can
> assign/close/etc bugs?
>
> Thank you in advance.
>
>
> https://issues.apache.org/jira/browse/MNG-6210
> https://issues.apache.org/jira/browse/MNG-6209
>
> --
> Regards,
> Igor
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

Re: is 3.5.1 open for business?

2017-04-07 Thread Igor Fedorenko

Thank you for quick response, Karl. I'll create feature branches and
push proposed fixes there.

Is there a preference between apache and github for code review
branches?

-- 
Regards,
Igor

On Fri, Apr 7, 2017, at 11:32 AM, Karl Heinz Marbaise wrote:
> Hi Igor,
> >>
> >> Also, does anyone know how to get my JIRA account fixed so I can
> >> assign/close/etc bugs?
> >
> > You are not allowed to do? Write an INFRA ticket...in the meantime I or
> > others can help here with that...
> 
> JIRA says your account does not exist...tried to assign 6210 to you...
> 
> Looks really like an INFRA subject...
> 
> Kind regards
> Karl Heinz
> 
> 
> -
> 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

Re: is 3.5.1 open for business?

2017-04-07 Thread Karl Heinz Marbaise


Hi Igor,


Also, does anyone know how to get my JIRA account fixed so I can
assign/close/etc bugs?


You are not allowed to do? Write an INFRA ticket...in the meantime I or
others can help here with that...


JIRA says your account does not exist...tried to assign 6210 to you...

Looks really like an INFRA subject...

Kind regards
Karl Heinz


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

Re: is 3.5.1 open for business?

2017-04-07 Thread Karl Heinz Marbaise


Hi Igor,

On 07/04/17 17:21, Igor Fedorenko wrote:

I have two of small-ish fixes I'd like to submit, so I was wondering if
master is open for 3.5.1 changes already or we want to give it little
more time in case we need to release any emergency patches.


If that's really necessary we can simply make a branch for that 
emergency patch...




Also, what is the general bug fixing protocol now, push to directly to
master and be prepared to revert or always go through a
pull-request-review process? I don't mind going the code review route,
but in this particular case both changes touch 1-2 lines of code not
counting regression test code, so I am not sure how much value formal
code review process will provide.


I would suggest to create appropriate branches per jira issue (MNG-6210, 
MNG-6209) for it and then we can see if IT's working well and afterwards 
merging them to master via fast-forward. This will prevent several 
commits/reverts on master...so we keep the history clean..





Also, does anyone know how to get my JIRA account fixed so I can
assign/close/etc bugs?


You are not allowed to do? Write an INFRA ticket...in the meantime I or 
others can help here with that...





Thank you in advance.


https://issues.apache.org/jira/browse/MNG-6210
https://issues.apache.org/jira/browse/MNG-6209



Kind regards
Karl Heinz Marbaise

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

is 3.5.1 open for business?

2017-04-07 Thread Igor Fedorenko

I have two of small-ish fixes I'd like to submit, so I was wondering if
master is open for 3.5.1 changes already or we want to give it little
more time in case we need to release any emergency patches.

Also, what is the general bug fixing protocol now, push to directly to
master and be prepared to revert or always go through a
pull-request-review process? I don't mind going the code review route,
but in this particular case both changes touch 1-2 lines of code not
counting regression test code, so I am not sure how much value formal
code review process will provide. 

Also, does anyone know how to get my JIRA account fixed so I can
assign/close/etc bugs?

Thank you in advance.


https://issues.apache.org/jira/browse/MNG-6210
https://issues.apache.org/jira/browse/MNG-6209

-- 
Regards,
Igor

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

[GitHub] maven issue #112: Fix snapshot regular expression

2017-04-07 Thread khmarbaise

Github user khmarbaise commented on the issue:

https://github.com/apache/maven/pull/112
  
First thanks for your pull request but it is really needed that you open a 
[JIRA ticket ](issues.apache.org/jira/browse/MNG) and furthermore it would be 
great if you could offer some unit tests which show the old behaviour and the 
new one which fix it by the appropriate fix.  Apart from that the commit 
message should contain a reference to the appropriate JIRA ticket cause it's 
can't followed later in the history and can't be seen in the release notes...



---
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

2017-04-07 Thread Petr Široký

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 
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 
> > 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
>

[GitHub] maven pull request #112: Fix snapshot regular expression

2017-04-07 Thread kevin-canadian

GitHub user kevin-canadian opened a pull request:

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

Fix snapshot regular expression

The snapshot regular expression should only match an explicit period.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kevin-canadian/maven patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/112.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #112


commit 4711e19eaf4bc1ef081d2940a2416289a5e60a89
Author: kevin-canadian 
Date:   2017-04-07T12:51:42Z

Fix snapshot regular expression

The snapshot regular expression should only match an explicit period.




---
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

2017-04-07 Thread Tibor Digana

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 
> 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

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

2017-04-07 Thread Tibor Digana

This is related to ForkConfiguration.
There is path created for the manifest.

On Fri, Apr 7, 2017 at 1:44 PM, Petr Široký  wrote:

> One more difference (bug?) I found:
>
> When I do:
>
> final URL parentUrl = this.getClass().getResource("/");
> System.out.println(parentUrl);
>
> the output is
> 'file:/home/psiroky/tmp/surefire-2.20-debug/target/test-classes//' -- note
> the duplicated slash at the end.
>
> I've done the same with 2.19.1 and the output is correct there --
> file:/home/psiroky/tmp/surefire-2.20-debug/target/test-classes/
>
> I believe, technically, the path is still valid, it's just that the tests
> are not expecting the duplicated slash and string comparison is failing on
> that.
>
> Petr
>
> 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 
> > 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

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

2017-04-07 Thread Petr Široký

One more difference (bug?) I found:

When I do:

final URL parentUrl = this.getClass().getResource("/");
System.out.println(parentUrl);

the output is
'file:/home/psiroky/tmp/surefire-2.20-debug/target/test-classes//' -- note
the duplicated slash at the end.

I've done the same with 2.19.1 and the output is correct there --
file:/home/psiroky/tmp/surefire-2.20-debug/target/test-classes/

I believe, technically, the path is still valid, it's just that the tests
are not expecting the duplicated slash and string comparison is failing on
that.

Petr

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 
> 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
>
>

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

2017-04-07 Thread Petr Široký

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  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
>

JDK 9 Developer Preview is now available on java.net

2017-04-07 Thread Rory O'Donnell


Hi Robert ,


 *JDK 9 Developer Preview is now available on java.net [1]
 *

Developer Preview milestone: - A reasonably stable build suitable for 
broad testing by the developer community is available.

JDK 9 Builds 163 and higher include all planned features.


*Attention annotation processing users and authors - * Request for 
feedback on annotation processing API changes made in JDK 9.


As has been done previously during Java SE 7 and Java SE 8, the JSR 269 
annotation processing API is undergoing a maintenance review (MR) as 
part of Java SE 9. Details of the changes in JDK 9 Early Access build 
163 & build 164 available here [2]


Please report experiences running processors under JDK 9 and feedback on 
the API changes to the compiler-dev mailing list.
(If you haven’t already subscribed to that list then please do so first, 
otherwise your message will be discarded as spam.)



Rgds, Rory

[1] https://jdk9.java.net/download/
[2] 
http://mail.openjdk.java.net/pipermail/compiler-dev/2017-April/010896.html


--
Rgds,Rory O'Donnell
Quality Engineering Manager

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

2017-04-07 Thread Stephen Connolly

23. Mark the version in JIRA as released

On 7 April 2017 at 09:40, Stephen Connolly 
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-
> maven/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-
> maven/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/
> infra/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  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 > om> wrote:
>>
>>> 11. Run the source release analyzer (https://github.com/stephenc/s
>>> ource-release-validator/commit/2e91ac959d0320a509e023b11b6389cc05719cdb)
>>> 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: No helping on the 3.5.0 release checklist...

2017-04-07 Thread Stephen Connolly

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-maven/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-maven/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/infra/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 
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/
> apache-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  com> wrote:
>
>> 11. Run the source release analyzer (https://github.com/stephenc/s
>> ource-release-validator/commit/2e91ac959d0320a509e023b11b6389cc05719cdb)
>> and reply to the vote with the results.
>>
>> On 3 April 2017 at 23:18, Stephen Connolly > om> 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
>>>
>>
>>
>

[RESULT] [VOTE] Release Apache Maven version 3.5.0

2017-04-07 Thread Stephen Connolly

Hi,

The vote has passed with the following result:

+1: Mark Derricutt, Dejan Stojadinović, Grzegorz Grzybek, Petr Široký, Igor
Fedorenko (binding), Anders Hammar, Manfred Moser, Karl Heinz Marbaise
(binding), Tibor Digana (binding), Fred Cooke, Raphael Ackermann, Hervé
Boutemy (binding), Olivier Lamy (binding), Arnaud Héritier (binding),
Stephen Connolly (binding), Elliot Metsger, Chas Honton, Thomas Collignon,
Robert Scholte (binding), Stephane Nicoll (binding), Dennis Kieselhorst

PMC quorum: Igor Fedorenko, Karl Heinz Marbaise, Tibor Digana, Hervé
Boutemy, Olivier Lamy, Arnaud Héritier, Stephen Connolly, Robert Scholte,
Stephane Nicoll

I will promote the artifacts to the central repository and proceed with the
rest of the release steps.

-Stephen

Re: [GitHub] maven-surefire issue #114: Parallel runner should not drop away runners that...

2017-04-07 Thread Tibor Digana

Sorry, I realized this was pending issue after release Vote started. Do not
worry, we will trigger a new version 2.20.1 in two weeks. Something is
already in good progress like this, so no reason to wait too long for
2.20.1.

On Fri, Apr 7, 2017 at 8:52 AM, flungo [via Maven] <
ml-node+s40175n5904930...@n5.nabble.com> wrote:

> Github user Fuud commented on the issue:
>
> https://github.com/apache/maven-surefire/pull/114
>
> any updates?
>
>
> ---
> 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 [hidden email]
>  or file a JIRA
> ticket
> with INFRA.
> ---
>
> -
> To unsubscribe, e-mail: [hidden email]
> 
> For additional commands, e-mail: [hidden email]
> 
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://maven.40175.n5.nabble.com/GitHub-maven-surefire-
> pull-request-114-Parallel-runner-should-not-drop-away-
> runne-tp5875060p5904930.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://maven.40175.n5.nabble.com/Re-GitHub-maven-surefire-issue-114-Parallel-runner-should-not-drop-away-runners-that-tp5904931.html
Sent from the Maven Developers mailing list archive at Nabble.com.

[GitHub] maven-surefire issue #114: Parallel runner should not drop away runners that...

2017-04-07 Thread Fuud

Github user Fuud commented on the issue:

https://github.com/apache/maven-surefire/pull/114
  
any updates?


---
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: [ANN] Apache Maven 3.5.0 Released

Re: [ANN] Apache Maven 3.5.0 Released

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

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

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

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

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

[ANN] Apache Maven 3.5.0 Released

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

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

Re: is 3.5.1 open for business?

Re: is 3.5.1 open for business?

Re: is 3.5.1 open for business?

Re: is 3.5.1 open for business?

Re: is 3.5.1 open for business?

is 3.5.1 open for business?

[GitHub] maven issue #112: Fix snapshot regular expression

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

[GitHub] maven pull request #112: Fix snapshot regular expression

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

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

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

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

JDK 9 Developer Preview is now available on java.net

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

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

[RESULT] [VOTE] Release Apache Maven version 3.5.0

Re: [GitHub] maven-surefire issue #114: Parallel runner should not drop away runners that...

[GitHub] maven-surefire issue #114: Parallel runner should not drop away runners that...

29 matches

Site Navigation

Mail list logo

Footer information