Re: [VOTE] Release Apache Maven 3.5.3

2018-03-02 Thread Arnaud Héritier 
+1

We add an entry in the release note about the know issue and we’ll release
a 3.5.4 with the Jansi fix ASAP

Le sam. 3 mars 2018 à 03:32, Manfred Moser  a
écrit :

> agreed
>
> +1 again ;-)
>
> Olivier Lamy wrote on 2018-03-02 18:14:
>
> > +1 to release as is
> >
> > On 3 March 2018 at 05:55,  wrote:
> >
> >> the issue is a multi-threading issue on Windows Jansi, then this affects
> >> people on Windows who try to use parallel build.
> >>
> >> I can commit on Jansi but not do a release: I can see this if a quick
> >> 1.17.1 is feasible...
> >>
> >> Regards,
> >>
> >> Hervé
> >>
> >> - Mail original -
> >> De: "Stephen Connolly" 
> >> À: "Maven Developers List" 
> >> Envoyé: Vendredi 2 Mars 2018 09:12:09
> >> Objet: Re: [VOTE] Release Apache Maven 3.5.3
> >>
> >> On Fri 2 Mar 2018 at 07:57, Sylwester Lachiewicz  >
> >> wrote:
> >>
> >> > Hi,
> >> > yes i was able to reproduce both errors (Dan and Guillaume) and fixes
> are
> >> > commited to JAnsi.
> >> > If someone one to retest - please build JAnsi from master.
> >> >
> >> > Fix #107 also shoud help with reseting colors after Ctrl-C.
> >> >
> >> > https://github.com/fusesource/jansi/issues/110
> >> > https://github.com/fusesource/jansi/issues/107
> >> >
> >>
> >> @Hervé wdyt should we release as is and we can 3.5.4 when jansi has a
> new
> >> release or shall we drop, wait and respin?
> >>
> >>
> >> > Regards,
> >> > Sylwester
> >> >
> >> > czw., 1 mar 2018 o 19:45 użytkownik Dan Tran 
> >> napisał:
> >> >
> >> > > Hi all
> >> > >
> >> > > Sylwester Lachiewicz provided a fix for jansi 1.18-SNAPSHOT  which
> >> > resolves
> >> > > my issue.  I am not able to reproduce antrun issue
> >> > >
> >> > >
> >> > > -Dan
> >> > >
> >> > > On Thu, Mar 1, 2018 at 5:00 AM, Stephane Nicoll <
> >> > stephane.nic...@gmail.com
> >> > > >
> >> > > wrote:
> >> > >
> >> > > > +1
> >> > > >
> >> > > > Thanks,
> >> > > > S.
> >> > > >
> >> > > > On Sat, Feb 24, 2018 at 11:01 PM, Stephen Connolly <
> >> > > > stephen.alan.conno...@gmail.com> wrote:
> >> > > >
> >> > > > > On 24 February 2018 at 22:00, Stephen Connolly <
> >> > > > > stephen.alan.conno...@gmail.com> wrote:
> >> > > > >
> >> > > > > > Hi,
> >> > > > > >
> >> > > > > > We solved 22 issues:
> >> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> > > > > > version=12341428=Text=12316922
> >> > > > > >
> >> > > > > > There are 381 issues left in JIRA for Maven core:
> >> > > > > > https://issues.apache.org/jira/issues/?jql=project%20%
> >> > > > > > 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> >> > > > > > 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >> > > > > >
> >> > > > > > Staging repo:
> >> > > > > >
> https://repository.apache.org/content/repositories/maven-1401/
> >> > > > > >
> >> > > > > > The distributable binaries and sources can be found here:
> >> > > > > > https://repository.apache.org/content/repositories/maven-
> >> > > > > > 1401/org/apache/maven/apache-maven/3.5.3/
> >> > > > > >
> >> > > > > > Specifically the zip, tarball and source archives can be found
> >> > here:
> >> > > > > > https://repository.apache.org/content/repositories/maven-
> >> > > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
> >> 3-bin.zip
> >> > > > > > https://repository.apache.org/content/repositories/maven-
> >> > > > > >
> >> > >
> 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.tar.gz
> >> > > > > > https://repository.apache.org/content/repositories/maven-
> >> > > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
> >> 3-src.zip
> >> > > > > > https://repository.apache.org/content/repositories/maven-
> >> > > > > >
> >> > >
> 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.tar.gz
> >> > > > > >
> >> > > > > > The release artifacts are staged for distribution in:
> >> > > > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
> >> > > > > >
> >> > > > > > Source release checksum(s):
> >> > > > > > apache-maven-3.5.3-src.tar.gz sha1:
> >> 60905d8b8b025b091f456ec25ad60d
> >> > > > > da56c26ad5
> >> > > > > > sha256:
> >> > 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd10
> >> > > > 7e19
> >> > > > > > apache-maven-3.5.3-src.zip: sha1:
> a9be51d571165261dfb2e0c8ecc6b4
> >> > > > > f1c4c96766
> >> > > > > > sha256:
> >> > 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7cc
> >> > > > bd57
> >> > > > > >
> >> > > > > > Git tag:
> >> > > > > >
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> >> > > > > > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297
> >> > > > > >
> >> > > > > > Staging site:
> >> > > > > > https://maven.apache.org/components/ref/3-LATEST/
> >> > > > > >
> >> > > > > > Vote open for 72 hours.
> >> > > > > >
> >> > > > > > [ ] +1
> >> > > > > > [ ] +0
> >> > > > > > [ ] -1
> >> > > > > >
> >> > > > > >

Re: [VOTE] Release Apache Maven 3.5.3

2018-03-02 Thread Manfred Moser 
agreed

+1 again ;-)

Olivier Lamy wrote on 2018-03-02 18:14:

> +1 to release as is
> 
> On 3 March 2018 at 05:55,  wrote:
> 
>> the issue is a multi-threading issue on Windows Jansi, then this affects
>> people on Windows who try to use parallel build.
>>
>> I can commit on Jansi but not do a release: I can see this if a quick
>> 1.17.1 is feasible...
>>
>> Regards,
>>
>> Hervé
>>
>> - Mail original -
>> De: "Stephen Connolly" 
>> À: "Maven Developers List" 
>> Envoyé: Vendredi 2 Mars 2018 09:12:09
>> Objet: Re: [VOTE] Release Apache Maven 3.5.3
>>
>> On Fri 2 Mar 2018 at 07:57, Sylwester Lachiewicz 
>> wrote:
>>
>> > Hi,
>> > yes i was able to reproduce both errors (Dan and Guillaume) and fixes are
>> > commited to JAnsi.
>> > If someone one to retest - please build JAnsi from master.
>> >
>> > Fix #107 also shoud help with reseting colors after Ctrl-C.
>> >
>> > https://github.com/fusesource/jansi/issues/110
>> > https://github.com/fusesource/jansi/issues/107
>> >
>>
>> @Hervé wdyt should we release as is and we can 3.5.4 when jansi has a new
>> release or shall we drop, wait and respin?
>>
>>
>> > Regards,
>> > Sylwester
>> >
>> > czw., 1 mar 2018 o 19:45 użytkownik Dan Tran 
>> napisał:
>> >
>> > > Hi all
>> > >
>> > > Sylwester Lachiewicz provided a fix for jansi 1.18-SNAPSHOT  which
>> > resolves
>> > > my issue.  I am not able to reproduce antrun issue
>> > >
>> > >
>> > > -Dan
>> > >
>> > > On Thu, Mar 1, 2018 at 5:00 AM, Stephane Nicoll <
>> > stephane.nic...@gmail.com
>> > > >
>> > > wrote:
>> > >
>> > > > +1
>> > > >
>> > > > Thanks,
>> > > > S.
>> > > >
>> > > > On Sat, Feb 24, 2018 at 11:01 PM, Stephen Connolly <
>> > > > stephen.alan.conno...@gmail.com> wrote:
>> > > >
>> > > > > On 24 February 2018 at 22:00, Stephen Connolly <
>> > > > > stephen.alan.conno...@gmail.com> wrote:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > We solved 22 issues:
>> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> > > > > > version=12341428=Text=12316922
>> > > > > >
>> > > > > > There are 381 issues left in JIRA for Maven core:
>> > > > > > https://issues.apache.org/jira/issues/?jql=project%20%
>> > > > > > 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
>> > > > > > 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>> > > > > >
>> > > > > > Staging repo:
>> > > > > > https://repository.apache.org/content/repositories/maven-1401/
>> > > > > >
>> > > > > > The distributable binaries and sources can be found here:
>> > > > > > https://repository.apache.org/content/repositories/maven-
>> > > > > > 1401/org/apache/maven/apache-maven/3.5.3/
>> > > > > >
>> > > > > > Specifically the zip, tarball and source archives can be found
>> > here:
>> > > > > > https://repository.apache.org/content/repositories/maven-
>> > > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
>> 3-bin.zip
>> > > > > > https://repository.apache.org/content/repositories/maven-
>> > > > > >
>> > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.tar.gz
>> > > > > > https://repository.apache.org/content/repositories/maven-
>> > > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
>> 3-src.zip
>> > > > > > https://repository.apache.org/content/repositories/maven-
>> > > > > >
>> > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.tar.gz
>> > > > > >
>> > > > > > The release artifacts are staged for distribution in:
>> > > > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
>> > > > > >
>> > > > > > Source release checksum(s):
>> > > > > > apache-maven-3.5.3-src.tar.gz sha1:
>> 60905d8b8b025b091f456ec25ad60d
>> > > > > da56c26ad5
>> > > > > > sha256:
>> > 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd10
>> > > > 7e19
>> > > > > > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4
>> > > > > f1c4c96766
>> > > > > > sha256:
>> > 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7cc
>> > > > bd57
>> > > > > >
>> > > > > > Git tag:
>> > > > > > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
>> > > > > > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297
>> > > > > >
>> > > > > > Staging site:
>> > > > > > https://maven.apache.org/components/ref/3-LATEST/
>> > > > > >
>> > > > > > Vote open for 72 hours.
>> > > > > >
>> > > > > > [ ] +1
>> > > > > > [ ] +0
>> > > > > > [ ] -1
>> > > > > >
>> > > > > > Thanks,
>> > > > > >
>> > > > > > Stephen.
>> > > > > >
>> > > > >
>> > > > >
>> > > > > $ sra https://repository.apache.org/content/repositories/maven-
>> 1401
>> > > > 3.5.3
>> > > > > Analyzer...
>> > > > >
>> > > > > stagingUrl:
>> > https://repository.apache.org/content/repositories/maven-
>> > > > 1401
>> > > > > groupId: org.apache.maven
>> > > > > artifactId: apache-maven
>> > > > > version: 3.5.3
>> > > > >
>> > > > > Source ZIP url exists.
>> > > > >

Re: [VOTE] Release Apache Maven 3.5.3

2018-03-02 Thread Olivier Lamy 
+1 to release as is

On 3 March 2018 at 05:55,  wrote:

> the issue is a multi-threading issue on Windows Jansi, then this affects
> people on Windows who try to use parallel build.
>
> I can commit on Jansi but not do a release: I can see this if a quick
> 1.17.1 is feasible...
>
> Regards,
>
> Hervé
>
> - Mail original -
> De: "Stephen Connolly" 
> À: "Maven Developers List" 
> Envoyé: Vendredi 2 Mars 2018 09:12:09
> Objet: Re: [VOTE] Release Apache Maven 3.5.3
>
> On Fri 2 Mar 2018 at 07:57, Sylwester Lachiewicz 
> wrote:
>
> > Hi,
> > yes i was able to reproduce both errors (Dan and Guillaume) and fixes are
> > commited to JAnsi.
> > If someone one to retest - please build JAnsi from master.
> >
> > Fix #107 also shoud help with reseting colors after Ctrl-C.
> >
> > https://github.com/fusesource/jansi/issues/110
> > https://github.com/fusesource/jansi/issues/107
> >
>
> @Hervé wdyt should we release as is and we can 3.5.4 when jansi has a new
> release or shall we drop, wait and respin?
>
>
> > Regards,
> > Sylwester
> >
> > czw., 1 mar 2018 o 19:45 użytkownik Dan Tran 
> napisał:
> >
> > > Hi all
> > >
> > > Sylwester Lachiewicz provided a fix for jansi 1.18-SNAPSHOT  which
> > resolves
> > > my issue.  I am not able to reproduce antrun issue
> > >
> > >
> > > -Dan
> > >
> > > On Thu, Mar 1, 2018 at 5:00 AM, Stephane Nicoll <
> > stephane.nic...@gmail.com
> > > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Thanks,
> > > > S.
> > > >
> > > > On Sat, Feb 24, 2018 at 11:01 PM, Stephen Connolly <
> > > > stephen.alan.conno...@gmail.com> wrote:
> > > >
> > > > > On 24 February 2018 at 22:00, Stephen Connolly <
> > > > > stephen.alan.conno...@gmail.com> wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > We solved 22 issues:
> > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > > version=12341428=Text=12316922
> > > > > >
> > > > > > There are 381 issues left in JIRA for Maven core:
> > > > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > > > > 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > > > > > 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> > > > > >
> > > > > > Staging repo:
> > > > > > https://repository.apache.org/content/repositories/maven-1401/
> > > > > >
> > > > > > The distributable binaries and sources can be found here:
> > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > > 1401/org/apache/maven/apache-maven/3.5.3/
> > > > > >
> > > > > > Specifically the zip, tarball and source archives can be found
> > here:
> > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
> 3-bin.zip
> > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > >
> > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.tar.gz
> > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
> 3-src.zip
> > > > > > https://repository.apache.org/content/repositories/maven-
> > > > > >
> > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.tar.gz
> > > > > >
> > > > > > The release artifacts are staged for distribution in:
> > > > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
> > > > > >
> > > > > > Source release checksum(s):
> > > > > > apache-maven-3.5.3-src.tar.gz sha1:
> 60905d8b8b025b091f456ec25ad60d
> > > > > da56c26ad5
> > > > > > sha256:
> > 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd10
> > > > 7e19
> > > > > > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4
> > > > > f1c4c96766
> > > > > > sha256:
> > 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7cc
> > > > bd57
> > > > > >
> > > > > > Git tag:
> > > > > > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> > > > > > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297
> > > > > >
> > > > > > Staging site:
> > > > > > https://maven.apache.org/components/ref/3-LATEST/
> > > > > >
> > > > > > Vote open for 72 hours.
> > > > > >
> > > > > > [ ] +1
> > > > > > [ ] +0
> > > > > > [ ] -1
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Stephen.
> > > > > >
> > > > >
> > > > >
> > > > > $ sra https://repository.apache.org/content/repositories/maven-
> 1401
> > > > 3.5.3
> > > > > Analyzer...
> > > > >
> > > > > stagingUrl:
> > https://repository.apache.org/content/repositories/maven-
> > > > 1401
> > > > > groupId: org.apache.maven
> > > > > artifactId: apache-maven
> > > > > version: 3.5.3
> > > > >
> > > > > Source ZIP url exists.
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.
> 3-src.zip
> > > > >
> > > > > Source ZIP SHA1 url exists.
> > > > >

Re: [VOTE] Release Apache Maven 3.5.3

2018-03-02 Thread herve . boutemy 
the issue is a multi-threading issue on Windows Jansi, then this affects people 
on Windows who try to use parallel build.

I can commit on Jansi but not do a release: I can see this if a quick 1.17.1 is 
feasible...

Regards,

Hervé

- Mail original -
De: "Stephen Connolly" 
À: "Maven Developers List" 
Envoyé: Vendredi 2 Mars 2018 09:12:09
Objet: Re: [VOTE] Release Apache Maven 3.5.3

On Fri 2 Mar 2018 at 07:57, Sylwester Lachiewicz 
wrote:

> Hi,
> yes i was able to reproduce both errors (Dan and Guillaume) and fixes are
> commited to JAnsi.
> If someone one to retest - please build JAnsi from master.
>
> Fix #107 also shoud help with reseting colors after Ctrl-C.
>
> https://github.com/fusesource/jansi/issues/110
> https://github.com/fusesource/jansi/issues/107
>

@Hervé wdyt should we release as is and we can 3.5.4 when jansi has a new
release or shall we drop, wait and respin?


> Regards,
> Sylwester
>
> czw., 1 mar 2018 o 19:45 użytkownik Dan Tran  napisał:
>
> > Hi all
> >
> > Sylwester Lachiewicz provided a fix for jansi 1.18-SNAPSHOT  which
> resolves
> > my issue.  I am not able to reproduce antrun issue
> >
> >
> > -Dan
> >
> > On Thu, Mar 1, 2018 at 5:00 AM, Stephane Nicoll <
> stephane.nic...@gmail.com
> > >
> > wrote:
> >
> > > +1
> > >
> > > Thanks,
> > > S.
> > >
> > > On Sat, Feb 24, 2018 at 11:01 PM, Stephen Connolly <
> > > stephen.alan.conno...@gmail.com> wrote:
> > >
> > > > On 24 February 2018 at 22:00, Stephen Connolly <
> > > > stephen.alan.conno...@gmail.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > We solved 22 issues:
> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > version=12341428=Text=12316922
> > > > >
> > > > > There are 381 issues left in JIRA for Maven core:
> > > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > > > 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > > > > 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> > > > >
> > > > > Staging repo:
> > > > > https://repository.apache.org/content/repositories/maven-1401/
> > > > >
> > > > > The distributable binaries and sources can be found here:
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > > 1401/org/apache/maven/apache-maven/3.5.3/
> > > > >
> > > > > Specifically the zip, tarball and source archives can be found
> here:
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > >
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.tar.gz
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > >
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.tar.gz
> > > > >
> > > > > The release artifacts are staged for distribution in:
> > > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
> > > > >
> > > > > Source release checksum(s):
> > > > > apache-maven-3.5.3-src.tar.gz sha1: 60905d8b8b025b091f456ec25ad60d
> > > > da56c26ad5
> > > > > sha256:
> 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd10
> > > 7e19
> > > > > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4
> > > > f1c4c96766
> > > > > sha256:
> 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7cc
> > > bd57
> > > > >
> > > > > Git tag:
> > > > > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> > > > > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297
> > > > >
> > > > > Staging site:
> > > > > https://maven.apache.org/components/ref/3-LATEST/
> > > > >
> > > > > Vote open for 72 hours.
> > > > >
> > > > > [ ] +1
> > > > > [ ] +0
> > > > > [ ] -1
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Stephen.
> > > > >
> > > >
> > > >
> > > > $ sra https://repository.apache.org/content/repositories/maven-1401
> > > 3.5.3
> > > > Analyzer...
> > > >
> > > > stagingUrl:
> https://repository.apache.org/content/repositories/maven-
> > > 1401
> > > > groupId: org.apache.maven
> > > > artifactId: apache-maven
> > > > version: 3.5.3
> > > >
> > > > Source ZIP url exists.
> > > > https://repository.apache.org/content/repositories/maven-
> > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip
> > > >
> > > > Source ZIP SHA1 url exists.
> > > > https://repository.apache.org/content/repositories/maven-
> > > >
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip.sha1
> > > >
> > > > Binary ZIP url exists.
> > > > https://repository.apache.org/content/repositories/maven-
> > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip
> > > >
> > > > Binary ZIP SHA1 url exists.
> > > >

Re: Surefire release?

2018-03-02 Thread Enrico Olivelli 
Il ven 2 mar 2018, 19:43 Tibor Digana  ha scritto:

> I will close the Jira Version and I will complete all preparation for the
> release vote tomorrow morning.
>

Great!
Enrico

>
> On Fri, Mar 2, 2018 at 6:02 PM, Enrico Olivelli 
> wrote:
>
> > I see SUREFIRE 1491 is on master, eo we have a green light?
> > Thank you Tibor
> >
> > Il gio 1 mar 2018, 22:38 Olivier Lamy  ha scritto:
> >
> > > Ok Sounds good.
> > > But could we just focus on a new release rather than new issues?
> > >
> > >
> > >
> > >
> > > On 1 March 2018 at 14:20, Tibor Digana  wrote:
> > >
> > > > There is a branch SUREFIRE-1491 waiting for pushing to master. It is
> > open
> > > > for everybody who want to check it:
> > > > https://git-wip-us.apache.org/repos/asf?p=maven-surefire.
> > > > git;a=shortlog;h=refs/heads/SUREFIRE-1491
> > > > Here is the Jenkins build link
> > > > https://builds.apache.org/job/maven-wip/job/maven-surefire/
> > > > job/SUREFIRE-1491/
> > > >
> > > > Cheers
> > > > Tibor
> > > >
> > > >
> > > > On Thu, Mar 1, 2018 at 4:24 AM, Olivier Lamy 
> wrote:
> > > >
> > > > > Hi
> > > > > Inline
> > > > >
> > > > > On 1 March 2018 at 12:55, Tibor Digana 
> > wrote:
> > > > >
> > > > > > Hi Olivier,
> > > > > >
> > > > > > Please do not make it yet - I am in progress with fixing.
> > > > > > I am still running several branches on Jenkins. The Jira issues
> in
> > > > 2.21.0
> > > > > > match branch name, as for instance today's SUREFIRE-1491.
> > > > > > After 1491 the next ones will be cosmetic changes - quite fast to
> > do.
> > > > > > I would like to start the vote in the weekend. So we have been
> > > working
> > > > > with
> > > > > > Robert Scholte and me quite a lot on this release, please let us
> > > finish
> > > > > it.
> > > > > >
> > > > >
> > > > > I don't mind doing myself the release. I don't have any need
> neither
> > > pay
> > > > > any attention of of having my name attached to a release!!
> > > > > I just want to get this done ASAP. As a user (a non friendly one in
> > > this
> > > > > case :-) ) I'm very disappointed to not be able to test my projects
> > > with
> > > > > jdk10.
> > > > > So I'm simply rocking the boat to get this done!
> > > > > So if you prefer doing the release by yourself please do it!
> > > > >
> > > > >
> > > > > > Then 3.0.0-M1 would be yours, Olivier and most probably everybody
> > > would
> > > > > > appreciate new API and Java 1.7 including me.
> > > > > >
> > > > > > In the next release 3.0.0-M1 we can cherrypick and squash commits
> > > from
> > > > > the
> > > > > > existing branch 3.0-rc1 together and you Olivier can make a
> > release.
> > > > > > The JUnit Users would expect release of our new provider asap, so
> > we
> > > > have
> > > > > > to cherrypick and squash commits from branch junit5 in Version
> > > 3.0.0-M2
> > > > > and
> > > > > > add a statement to documentation saying that JUnit5 has
> incomplete
> > > > > > feature-matrix against JUnit47 and we call it experimental
> provider
> > > > > because
> > > > > > we do not have all feature ITs covered.
> > > > > > Both (3.0-API and JUnit5) are actually very urgent, so they
> should
> > > > follow
> > > > > > right after current Version 2.21.0.
> > > > > >
> > > > >
> > > > > Sure so we don't have to delay 2.21.0
> > > > >
> > > > >
> > > > > >
> > > > > > Why M1, M2, etc, because we with Kristian and Andreas wanted to
> > > change
> > > > > the
> > > > > > system properties of config params to something like surefire.*
> and
> > > > > > failsafe.* and include interfaces to some config params with
> > > > > > "implements=..." which would customize the plugins without asking
> > us
> > > to
> > > > > do
> > > > > > in ASF. Some prototype was done but it did not go with
> > > > "implements=...".
> > > > > >
> > > > > > Additionally, we have to release 3.0.0-M3 with reworked
> > communication
> > > > > > between processes (maven -> surefire) because the execution hangs
> > > with
> > > > > > pipes and I found a bug in JDK in maven-shared-utils. We have
> some
> > > > > > prototype with sockets but pipes must stay as an config
> > alternative.
> > > > This
> > > > > > includes changes in the data format sent over pipes and sockets
> > which
> > > > is
> > > > > on
> > > > > > my PC and not in any public branch. With this fix we will close
> all
> > > > known
> > > > > > critical Jiras.
> > > > > > I could not do it earlier, sorry. There's been a quite a lot of
> > > > > > requirements so far from Users and us ASF.
> > > > > >
> > > > > > Cheers
> > > > > > Tibor
> > > > > >
> > > > > >
> > > > > > On Thu, Mar 1, 2018 at 12:14 AM, Olivier Lamy 
> > > > wrote:
> > > > > >
> > > > > > > Hi
> > > > > > > Any objections to cut a release?
> > > > > > > If not, I can do this early next week
> > > > > > > Cheers
> > > > > > > --
> > > > > > > Olivier Lamy
> > > > > > >

Re: Surefire release?

2018-03-02 Thread Tibor Digana 
I will close the Jira Version and I will complete all preparation for the
release vote tomorrow morning.

On Fri, Mar 2, 2018 at 6:02 PM, Enrico Olivelli  wrote:

> I see SUREFIRE 1491 is on master, eo we have a green light?
> Thank you Tibor
>
> Il gio 1 mar 2018, 22:38 Olivier Lamy  ha scritto:
>
> > Ok Sounds good.
> > But could we just focus on a new release rather than new issues?
> >
> >
> >
> >
> > On 1 March 2018 at 14:20, Tibor Digana  wrote:
> >
> > > There is a branch SUREFIRE-1491 waiting for pushing to master. It is
> open
> > > for everybody who want to check it:
> > > https://git-wip-us.apache.org/repos/asf?p=maven-surefire.
> > > git;a=shortlog;h=refs/heads/SUREFIRE-1491
> > > Here is the Jenkins build link
> > > https://builds.apache.org/job/maven-wip/job/maven-surefire/
> > > job/SUREFIRE-1491/
> > >
> > > Cheers
> > > Tibor
> > >
> > >
> > > On Thu, Mar 1, 2018 at 4:24 AM, Olivier Lamy  wrote:
> > >
> > > > Hi
> > > > Inline
> > > >
> > > > On 1 March 2018 at 12:55, Tibor Digana 
> wrote:
> > > >
> > > > > Hi Olivier,
> > > > >
> > > > > Please do not make it yet - I am in progress with fixing.
> > > > > I am still running several branches on Jenkins. The Jira issues in
> > > 2.21.0
> > > > > match branch name, as for instance today's SUREFIRE-1491.
> > > > > After 1491 the next ones will be cosmetic changes - quite fast to
> do.
> > > > > I would like to start the vote in the weekend. So we have been
> > working
> > > > with
> > > > > Robert Scholte and me quite a lot on this release, please let us
> > finish
> > > > it.
> > > > >
> > > >
> > > > I don't mind doing myself the release. I don't have any need neither
> > pay
> > > > any attention of of having my name attached to a release!!
> > > > I just want to get this done ASAP. As a user (a non friendly one in
> > this
> > > > case :-) ) I'm very disappointed to not be able to test my projects
> > with
> > > > jdk10.
> > > > So I'm simply rocking the boat to get this done!
> > > > So if you prefer doing the release by yourself please do it!
> > > >
> > > >
> > > > > Then 3.0.0-M1 would be yours, Olivier and most probably everybody
> > would
> > > > > appreciate new API and Java 1.7 including me.
> > > > >
> > > > > In the next release 3.0.0-M1 we can cherrypick and squash commits
> > from
> > > > the
> > > > > existing branch 3.0-rc1 together and you Olivier can make a
> release.
> > > > > The JUnit Users would expect release of our new provider asap, so
> we
> > > have
> > > > > to cherrypick and squash commits from branch junit5 in Version
> > 3.0.0-M2
> > > > and
> > > > > add a statement to documentation saying that JUnit5 has incomplete
> > > > > feature-matrix against JUnit47 and we call it experimental provider
> > > > because
> > > > > we do not have all feature ITs covered.
> > > > > Both (3.0-API and JUnit5) are actually very urgent, so they should
> > > follow
> > > > > right after current Version 2.21.0.
> > > > >
> > > >
> > > > Sure so we don't have to delay 2.21.0
> > > >
> > > >
> > > > >
> > > > > Why M1, M2, etc, because we with Kristian and Andreas wanted to
> > change
> > > > the
> > > > > system properties of config params to something like surefire.* and
> > > > > failsafe.* and include interfaces to some config params with
> > > > > "implements=..." which would customize the plugins without asking
> us
> > to
> > > > do
> > > > > in ASF. Some prototype was done but it did not go with
> > > "implements=...".
> > > > >
> > > > > Additionally, we have to release 3.0.0-M3 with reworked
> communication
> > > > > between processes (maven -> surefire) because the execution hangs
> > with
> > > > > pipes and I found a bug in JDK in maven-shared-utils. We have some
> > > > > prototype with sockets but pipes must stay as an config
> alternative.
> > > This
> > > > > includes changes in the data format sent over pipes and sockets
> which
> > > is
> > > > on
> > > > > my PC and not in any public branch. With this fix we will close all
> > > known
> > > > > critical Jiras.
> > > > > I could not do it earlier, sorry. There's been a quite a lot of
> > > > > requirements so far from Users and us ASF.
> > > > >
> > > > > Cheers
> > > > > Tibor
> > > > >
> > > > >
> > > > > On Thu, Mar 1, 2018 at 12:14 AM, Olivier Lamy 
> > > wrote:
> > > > >
> > > > > > Hi
> > > > > > Any objections to cut a release?
> > > > > > If not, I can do this early next week
> > > > > > Cheers
> > > > > > --
> > > > > > Olivier Lamy
> > > > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Olivier Lamy
> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > >
> > >
> >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
> --
>
>
> -- Enrico Olivelli
>

Re: Surefire release?

2018-03-02 Thread Enrico Olivelli 
I see SUREFIRE 1491 is on master, eo we have a green light?
Thank you Tibor

Il gio 1 mar 2018, 22:38 Olivier Lamy  ha scritto:

> Ok Sounds good.
> But could we just focus on a new release rather than new issues?
>
>
>
>
> On 1 March 2018 at 14:20, Tibor Digana  wrote:
>
> > There is a branch SUREFIRE-1491 waiting for pushing to master. It is open
> > for everybody who want to check it:
> > https://git-wip-us.apache.org/repos/asf?p=maven-surefire.
> > git;a=shortlog;h=refs/heads/SUREFIRE-1491
> > Here is the Jenkins build link
> > https://builds.apache.org/job/maven-wip/job/maven-surefire/
> > job/SUREFIRE-1491/
> >
> > Cheers
> > Tibor
> >
> >
> > On Thu, Mar 1, 2018 at 4:24 AM, Olivier Lamy  wrote:
> >
> > > Hi
> > > Inline
> > >
> > > On 1 March 2018 at 12:55, Tibor Digana  wrote:
> > >
> > > > Hi Olivier,
> > > >
> > > > Please do not make it yet - I am in progress with fixing.
> > > > I am still running several branches on Jenkins. The Jira issues in
> > 2.21.0
> > > > match branch name, as for instance today's SUREFIRE-1491.
> > > > After 1491 the next ones will be cosmetic changes - quite fast to do.
> > > > I would like to start the vote in the weekend. So we have been
> working
> > > with
> > > > Robert Scholte and me quite a lot on this release, please let us
> finish
> > > it.
> > > >
> > >
> > > I don't mind doing myself the release. I don't have any need neither
> pay
> > > any attention of of having my name attached to a release!!
> > > I just want to get this done ASAP. As a user (a non friendly one in
> this
> > > case :-) ) I'm very disappointed to not be able to test my projects
> with
> > > jdk10.
> > > So I'm simply rocking the boat to get this done!
> > > So if you prefer doing the release by yourself please do it!
> > >
> > >
> > > > Then 3.0.0-M1 would be yours, Olivier and most probably everybody
> would
> > > > appreciate new API and Java 1.7 including me.
> > > >
> > > > In the next release 3.0.0-M1 we can cherrypick and squash commits
> from
> > > the
> > > > existing branch 3.0-rc1 together and you Olivier can make a release.
> > > > The JUnit Users would expect release of our new provider asap, so we
> > have
> > > > to cherrypick and squash commits from branch junit5 in Version
> 3.0.0-M2
> > > and
> > > > add a statement to documentation saying that JUnit5 has incomplete
> > > > feature-matrix against JUnit47 and we call it experimental provider
> > > because
> > > > we do not have all feature ITs covered.
> > > > Both (3.0-API and JUnit5) are actually very urgent, so they should
> > follow
> > > > right after current Version 2.21.0.
> > > >
> > >
> > > Sure so we don't have to delay 2.21.0
> > >
> > >
> > > >
> > > > Why M1, M2, etc, because we with Kristian and Andreas wanted to
> change
> > > the
> > > > system properties of config params to something like surefire.* and
> > > > failsafe.* and include interfaces to some config params with
> > > > "implements=..." which would customize the plugins without asking us
> to
> > > do
> > > > in ASF. Some prototype was done but it did not go with
> > "implements=...".
> > > >
> > > > Additionally, we have to release 3.0.0-M3 with reworked communication
> > > > between processes (maven -> surefire) because the execution hangs
> with
> > > > pipes and I found a bug in JDK in maven-shared-utils. We have some
> > > > prototype with sockets but pipes must stay as an config alternative.
> > This
> > > > includes changes in the data format sent over pipes and sockets which
> > is
> > > on
> > > > my PC and not in any public branch. With this fix we will close all
> > known
> > > > critical Jiras.
> > > > I could not do it earlier, sorry. There's been a quite a lot of
> > > > requirements so far from Users and us ASF.
> > > >
> > > > Cheers
> > > > Tibor
> > > >
> > > >
> > > > On Thu, Mar 1, 2018 at 12:14 AM, Olivier Lamy 
> > wrote:
> > > >
> > > > > Hi
> > > > > Any objections to cut a release?
> > > > > If not, I can do this early next week
> > > > > Cheers
> > > > > --
> > > > > Olivier Lamy
> > > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Olivier Lamy
> > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > >
> >
>
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
-- 


-- Enrico Olivelli

delayed wagon

2018-03-02 Thread Basin Ilya 
Hi.
Some people might be frustrated that deploying artifacts to scm puts each file 
in a separate commit. At least, I was and I created a maven extension that 
solves this:

https://github.com/basinilya/wagon-delayed/

This extension overrides the default WagonProvider implementation. The 
difference is: if an "scm" wagon is requested, then this new provider wraps the 
wagon with a
DelayedWagon instance. This DelayedWagon delays all put operations until the 
disconnect() method is called and then it performs a single putDirectory() call.

Along the way, I fixed several bugs in the maven-scm and the maven-wagon 
projects without breaking backward compatibility. They're available as pull 
requests or in my
github forks of these two projects.

wagon-delayed depends on these fixes. Among its unit tests there's a demo test 
case that calls `mvn deploy` to a local test svn repo.

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

Re: jira contributor status?

2018-03-02 Thread Robert Scholte 

hi Sean,

thank you for the patch, which already makes you a contributor.
To be able to apply patches you need to be a Maven committer.
If you want to become a committer, please read the Guide Commmitter  
School[1]
In case of your patch for MJAVADOC-444, you have to focus on #2 and  
further.


thanks,
Robert

[1] https://maven.apache.org/guides/development/guide-committer-school

On Fri, 02 Mar 2018 15:36:15 +0100, Sean Busbey  wrote:


Hi!

Could someone give me contributor status in jira so I can assign  
MJAVADOC-444 to myself and put it in patch available status?


-
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

jira contributor status?

2018-03-02 Thread Sean Busbey 
Hi!

Could someone give me contributor status in jira so I can assign MJAVADOC-444 
to myself and put it in patch available status?

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

Re: surefire-junit47 depends on dummy:dummy:jar:1.0?

2018-03-02 Thread Alex O'Ree 
I was about to post the stack trace when i more carefully read the output.
This dev box is not internet connected by the way.
It was missing the following
- dummy:dummy:jar:1.0
- org.apache.maven.surefire:surefire47:jar:2.19.1

The 'dummy' part threw me off, but after syncing surefire47 and it's
transitives, i'm up and running.

But where does dummy come in? I don't see it declared as a dependency and
there's no jar anywhere


On Thu, Mar 1, 2018 at 4:33 PM, Enrico Olivelli  wrote:

> Alex,
> Can you share the stack trace of the error?
> If the message is not enough clear you can -X to the conmand line, like
>
> mvn test -X
>
> Cheers
> Enrico
>
> Il gio 1 mar 2018, 18:35 Alex O'Ree  ha scritto:
>
> > Can anyone shed light on the dummy:dummy jar file that surefire seems to
> > need? I don't see it in mvnrepository nor in repo.maven.apache.org.
> >
> > I'm using 2.19.1 of the surefire plugin. I added the following changes to
> > the plugin config and now it's complaining about artifact resolution
> >
> > classesAndMethods<
> threadCount>4
> > 
> >
> > Where can i find this jar?
> >
> --
>
>
> -- Enrico Olivelli
>

JDK 10: Release Candidate & JDK 11 Early Access builds available

2018-03-02 Thread Rory O'Donnell 

  Hi Robert ,

Can you confirm the fix in JDK 11

 * JDK-8193802 -
   Apache Maven
 o NullPointerException from JarFileSystem.getVersionMap()


*JDK 10 build 45 is our JDK 10 Release Candidate and now available at 
http://jdk.java.net/10/*


 * Schedule, status & features
 o http://openjdk.java.net/projects/jdk/10/
 * Release Notes
 o http://jdk.java.net/10/release-notes
 * Summary of changes in b45:
 o JDK-8198658  -
   Docs still point to JDK 9 docs

*JDK 11 EA build 3, under both the GPL and Oracle EA licenses, are now 
available at **http://jdk.java.net/11**.*


 * Schedule, status & features
 o http://openjdk.java.net/projects/jdk/11/
 * Release Notes:
 o http://jdk.java.net/11/release-notes
 * Summary of changes
 o https://download.java.net/java/early_access/jdk11/2/jdk-11+2.html
 * JEPs targeted to JDK 11, so far
 o 309: Dynamic Class-File Constants 
 o 318: Epsilon: An Arbitrarily Low-Overhead Garbage Collector
   
 o *320: **Remove the Java EE and CORBA Modules
   *
   **
 + ** *This build includes JEP 320, so build is significantly
   smaller (nine fewer modules, 22 fewer megabyteson Linux/x64).*
 o 323: Local-Variable Syntax for Lambda Parameters
   
 * Open Source Project fixes in JDK 11 build 1
 o JDK-8195096 -
   Apache Tomcat
 + Exception with custom LogManager on starting Apache Tomcat
 o JDK-8193802 -
   Apache Maven
 + NullPointerException from JarFileSystem.getVersionMap()
 o JDK-8191842  -
   jOOQ
 + JShell: Inferred type information is lost when assigning
   types to a "var"

Finally, the Crypto roadmap 
 was updated - 
23-Feb-2018**

**

 * Add support for AEAD TLS Cipher Suites
 o Target date changed from 2018-04-17 to 2018-07-17


Regards,
Rory

--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

Re: [VOTE] Release Apache Maven 3.5.3

2018-03-02 Thread Stephen Connolly 
On Fri 2 Mar 2018 at 07:57, Sylwester Lachiewicz 
wrote:

> Hi,
> yes i was able to reproduce both errors (Dan and Guillaume) and fixes are
> commited to JAnsi.
> If someone one to retest - please build JAnsi from master.
>
> Fix #107 also shoud help with reseting colors after Ctrl-C.
>
> https://github.com/fusesource/jansi/issues/110
> https://github.com/fusesource/jansi/issues/107
>

@Hervé wdyt should we release as is and we can 3.5.4 when jansi has a new
release or shall we drop, wait and respin?


> Regards,
> Sylwester
>
> czw., 1 mar 2018 o 19:45 użytkownik Dan Tran  napisał:
>
> > Hi all
> >
> > Sylwester Lachiewicz provided a fix for jansi 1.18-SNAPSHOT  which
> resolves
> > my issue.  I am not able to reproduce antrun issue
> >
> >
> > -Dan
> >
> > On Thu, Mar 1, 2018 at 5:00 AM, Stephane Nicoll <
> stephane.nic...@gmail.com
> > >
> > wrote:
> >
> > > +1
> > >
> > > Thanks,
> > > S.
> > >
> > > On Sat, Feb 24, 2018 at 11:01 PM, Stephen Connolly <
> > > stephen.alan.conno...@gmail.com> wrote:
> > >
> > > > On 24 February 2018 at 22:00, Stephen Connolly <
> > > > stephen.alan.conno...@gmail.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > We solved 22 issues:
> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > > version=12341428=Text=12316922
> > > > >
> > > > > There are 381 issues left in JIRA for Maven core:
> > > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > > > 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> > > > > 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> > > > >
> > > > > Staging repo:
> > > > > https://repository.apache.org/content/repositories/maven-1401/
> > > > >
> > > > > The distributable binaries and sources can be found here:
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > > 1401/org/apache/maven/apache-maven/3.5.3/
> > > > >
> > > > > Specifically the zip, tarball and source archives can be found
> here:
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > >
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.tar.gz
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip
> > > > > https://repository.apache.org/content/repositories/maven-
> > > > >
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.tar.gz
> > > > >
> > > > > The release artifacts are staged for distribution in:
> > > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.3
> > > > >
> > > > > Source release checksum(s):
> > > > > apache-maven-3.5.3-src.tar.gz sha1: 60905d8b8b025b091f456ec25ad60d
> > > > da56c26ad5
> > > > > sha256:
> 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd10
> > > 7e19
> > > > > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4
> > > > f1c4c96766
> > > > > sha256:
> 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7cc
> > > bd57
> > > > >
> > > > > Git tag:
> > > > > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> > > > > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297
> > > > >
> > > > > Staging site:
> > > > > https://maven.apache.org/components/ref/3-LATEST/
> > > > >
> > > > > Vote open for 72 hours.
> > > > >
> > > > > [ ] +1
> > > > > [ ] +0
> > > > > [ ] -1
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Stephen.
> > > > >
> > > >
> > > >
> > > > $ sra https://repository.apache.org/content/repositories/maven-1401
> > > 3.5.3
> > > > Analyzer...
> > > >
> > > > stagingUrl:
> https://repository.apache.org/content/repositories/maven-
> > > 1401
> > > > groupId: org.apache.maven
> > > > artifactId: apache-maven
> > > > version: 3.5.3
> > > >
> > > > Source ZIP url exists.
> > > > https://repository.apache.org/content/repositories/maven-
> > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip
> > > >
> > > > Source ZIP SHA1 url exists.
> > > > https://repository.apache.org/content/repositories/maven-
> > > >
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip.sha1
> > > >
> > > > Binary ZIP url exists.
> > > > https://repository.apache.org/content/repositories/maven-
> > > > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip
> > > >
> > > > Binary ZIP SHA1 url exists.
> > > > https://repository.apache.org/content/repositories/maven-
> > > >
> > 1401/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip.sha1
> > > >
> > > > Calculated SHA1 of source ZIP matches published SHA1 of source ZIP.
> > > > a9be51d571165261dfb2e0c8ecc6b4f1c4c96766
> > > >
> > > > Calculated SHA1 of binary ZIP matches published SHA1 of binary ZIP.
> > > > 4a4844990333e2548540729ce9ab57f52a63148d
> > > >
> > > > Git revision of release as determined from
> > > >