Re: [VOTE] Release Apache Maven Verifier version 1.7.2

2020-05-05 Thread Hervé BOUTEMY
+1 binary artifacts reproduced with JDK8 and crlf newlines Le dimanche 3 mai 2020, 16:18:18 CEST Robert Scholte a écrit : > Hi, > > My apologies for asking for another vote on this library due to a blocking > issue related to Maven Wrapper. > > We solved 1 blocking issue: > https://issues.apach

[GitHub] [maven-site] elharo opened a new pull request #162: [MNGSITE-393] remove still more very outdated content

2020-05-05 Thread GitBox
elharo opened a new pull request #162: URL: https://github.com/apache/maven-site/pull/162 @slachiewicz This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [maven-site] slachiewicz commented on pull request #161: [MNGSITE-393] remove more outdated and 404 content

2020-05-05 Thread GitBox
slachiewicz commented on pull request #161: URL: https://github.com/apache/maven-site/pull/161#issuecomment-624080725 We can skipbook about maven 2 This is an automated message from the Apache Git Service. To respond to the m

[GitHub] [maven-site] elharo opened a new pull request #161: [MNGSITE-393] remove more outdated and 404 content

2020-05-05 Thread GitBox
elharo opened a new pull request #161: URL: https://github.com/apache/maven-site/pull/161 @slachiewicz This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [maven-site] elharo opened a new pull request #160: [MNGSITE-393] remove some outdated books and 404 links

2020-05-05 Thread GitBox
elharo opened a new pull request #160: URL: https://github.com/apache/maven-site/pull/160 @michael-o This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

Re: [VOTE] Release Apache Maven Verifier version 1.7.2

2020-05-05 Thread Olivier Lamy
+1 On Mon, 4 May 2020 at 00:18, Robert Scholte wrote: > Hi, > > My apologies for asking for another vote on this library due to a blocking > issue related to Maven Wrapper. > > We solved 1 blocking issue: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12347

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.22.3

2020-05-05 Thread Tibor Digana
I wanted to copy paste that part of AbstractSurefireMojo which solves this problem in this release but i was too lazy to do it. I can do it and we can collaborate on the GitHub in a pullrequest - the resolver's call will be different, that's the only thing, but doable. The code is more simple now,

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.22.3

2020-05-05 Thread Stephane Nicoll
I don't see releasing Surefire 3.0 as fixing this problem. Users having an upgrade policy in place would still not be able to upgrade to 3.0 anyway. We are talking about a backward incompatible change in a maintenance release of the Surefire plugin. As much as I welcome 3.0 to be GA, that won't cha

Re: [VOTE] Release Apache Maven Verifier version 1.7.2

2020-05-05 Thread Tibor Digana
+1, sha512 ok, build ok On Sun, May 3, 2020 at 4:18 PM Robert Scholte wrote: > > Hi, > > My apologies for asking for another vote on this library due to a blocking > issue related to Maven Wrapper. > > We solved 1 blocking issue: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId

Re: [VOTE] Release Apache Maven Verifier version 1.7.2

2020-05-05 Thread Robert Scholte
+1 On 3-5-2020 16:18:18, Robert Scholte wrote: Hi, My apologies for asking for another vote on this library due to a blocking issue related to Maven Wrapper. We solved 1 blocking issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12347858&styleName=Text

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.22.3

2020-05-05 Thread Tibor Digana
I would go to the original question. How important is the issue [1] for the user? If it is not important, then we can cut the release with one fix SUREFIRE-1679. If it is important, which does not seem so yet, then we can backport smart resolver from the master. Technically possible! [1]: https:/