[RESULT] [VOTE] Release Apache Maven 3.5.3
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: 60905d8b8b025b091f456ec25ad60dda56c26ad5 > sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19 > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4f1c4c96766 > sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57 > > 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. > Results: +1: Mirko Friedenhagen, Karl Heinz Marbaise (pmc), Guillaume Boué (pmc), Olivier Lamy (pmc), Arnaud Héritier (pmc), Robert Scholte (pmc), Grzegorz Grzybek, Stephane Nicoll (pmc), Manfred Moser, Tibor Digana (pmc), Hervé Boutemy (pmc), Stephen Connolly (pmc) +0: -1: The vote has passed (i.e. there is a majority of all votes cast in favour of the release) and has met the Apache Foundation's legal requirements for releasing (i.e. there must be at least three pmc votes) I will now proceed with finalizing the release.
Re: [VOTE] Release Apache Maven 3.5.3
+1 I'll tally up the votes this evening and push the release On 4 March 2018 at 16:01, Stephane Nicoll <stephane.nic...@gmail.com> wrote: > I already cast my +1 but, +1 to release as is. > > S. > > On Fri, Mar 2, 2018 at 8:55 PM, <herve.bout...@free.fr> 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... > Hervé could you add the details of this issue to the draft release notes? Or even just somebody describe the details here and I will update the release notes this evening myself. > > > > Regards, > > > > Hervé > > > > - Mail original - > > De: "Stephen Connolly" <stephen.alan.conno...@gmail.com> > > À: "Maven Developers List" <dev@maven.apache.org> > > 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 <slachiew...@gmail.com> > > 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 <dant...@gmail.com> > > 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
Re: [VOTE] Release Apache Maven 3.5.3
I already cast my +1 but, +1 to release as is. S. On Fri, Mar 2, 2018 at 8:55 PM, <herve.bout...@free.fr> 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" <stephen.alan.conno...@gmail.com> > À: "Maven Developers List" <dev@maven.apache.org> > 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 <slachiew...@gmail.com> > 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 <dant...@gmail.com> > 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:
Re: [VOTE] Release Apache Maven 3.5.3
Hi, +1 from this approach as well.. We should get 3.5.3 out of the door.. Kind regards Karl Heinz Marbaise On 03/03/18 08:42, Arnaud Héritier wrote: +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 <manf...@simpligility.com> 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, <herve.bout...@free.fr> 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" <stephen.alan.conno...@gmail.com> À: "Maven Developers List" <dev@maven.apache.org> 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 <slachiew...@gmail.com 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 <dant...@gmail.com> 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
Re: [VOTE] Release Apache Maven 3.5.3
+1 both for immediate vote and for the plan to release as is then releasing ASAP 3.5.4 Regards, Hervé - Mail original - De: "Mirko Friedenhagen" <mfriedenha...@gmail.com> À: "Maven Developers List" <dev@maven.apache.org> Envoyé: Samedi 3 Mars 2018 13:42:43 Objet: Re: [VOTE] Release Apache Maven 3.5.3 I would suggest releasing as is as well. State in the announcement that there might be a problem with parallel builds on Windows, workaround with batch mode is easy anyway. And if 3.5.4 only contains the fixed jansi dependency, releasing should be fast and simple. Best regards Mirko -- Sent from my mobile Am 03.03.2018 03:32 schrieb "Manfred Moser" <manf...@simpligility.com>: > agreed > > +1 again ;-) > > Olivier Lamy wrote on 2018-03-02 18:14: > > > +1 to release as is > > > > On 3 March 2018 at 05:55, <herve.bout...@free.fr> 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" <stephen.alan.conno...@gmail.com> > >> À: "Maven Developers List" <dev@maven.apache.org> > >> 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 <slachiew...@gmail.com > > > >> 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 <dant...@gmail.com> > >> 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- > >> > &
Re: [VOTE] Release Apache Maven 3.5.3
I would suggest releasing as is as well. State in the announcement that there might be a problem with parallel builds on Windows, workaround with batch mode is easy anyway. And if 3.5.4 only contains the fixed jansi dependency, releasing should be fast and simple. Best regards Mirko -- Sent from my mobile Am 03.03.2018 03:32 schrieb "Manfred Moser" <manf...@simpligility.com>: > agreed > > +1 again ;-) > > Olivier Lamy wrote on 2018-03-02 18:14: > > > +1 to release as is > > > > On 3 March 2018 at 05:55, <herve.bout...@free.fr> 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" <stephen.alan.conno...@gmail.com> > >> À: "Maven Developers List" <dev@maven.apache.org> > >> 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 <slachiew...@gmail.com > > > >> 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 <dant...@gmail.com> > >> 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- > >> > > > > &
Re: [VOTE] Release Apache Maven 3.5.3
+1 from me. I did not find any issue. On Sat, Feb 24, 2018 at 11:00 PM, 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: > 60905d8b8b025b091f456ec25ad60dda56c26ad5 > sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19 > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4f1c4c96766 > sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57 > > 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. >
Re: [VOTE] Release Apache Maven 3.5.3
+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 <manf...@simpligility.com> 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, <herve.bout...@free.fr> 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" <stephen.alan.conno...@gmail.com> > >> À: "Maven Developers List" <dev@maven.apache.org> > >> 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 <slachiew...@gmail.com > > > >> 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 <dant...@gmail.com> > >> 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- &g
Re: [VOTE] Release Apache Maven 3.5.3
agreed +1 again ;-) Olivier Lamy wrote on 2018-03-02 18:14: > +1 to release as is > > On 3 March 2018 at 05:55, <herve.bout...@free.fr> 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" <stephen.alan.conno...@gmail.com> >> À: "Maven Developers List" <dev@maven.apache.org> >> 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 <slachiew...@gmail.com> >> 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 <dant...@gmail.com> >> 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/di
Re: [VOTE] Release Apache Maven 3.5.3
+1 to release as is On 3 March 2018 at 05:55, <herve.bout...@free.fr> 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" <stephen.alan.conno...@gmail.com> > À: "Maven Developers List" <dev@maven.apache.org> > 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 <slachiew...@gmail.com> > 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 <dant...@gmail.com> > 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 > > &g
Re: [VOTE] Release Apache Maven 3.5.3
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" <stephen.alan.conno...@gmail.com> À: "Maven Developers List" <dev@maven.apache.org> 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 <slachiew...@gmail.com> 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 <dant...@gmail.com> 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
Re: [VOTE] Release Apache Maven 3.5.3
On Fri 2 Mar 2018 at 07:57, Sylwester Lachiewiczwrote: > 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 > > > >
Re: [VOTE] Release Apache Maven 3.5.3
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 Regards, Sylwester czw., 1 mar 2018 o 19:45 użytkownik Dan Trannapisał: > 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 > > 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 > > > maven-core-3.5.3.jar:org/apache/maven/messages/build. > > > properties(buildNumber): > > > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297 > > > > > > Files that are present in the source distribution but not in the source > > > revision: > > > DEPENDENCIES > > > > > >
Re: [VOTE] Release Apache Maven 3.5.3
Used on a bunch of project for a couple of days now without problems. +1 Manfred Stephen Connolly wrote on 2018-02-24 16:00: > 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: > 60905d8b8b025b091f456ec25ad60dda56c26ad5 > sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19 > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4f1c4c96766 > sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57 > > 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. > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.5.3
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 Nicollwrote: > +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 > > maven-core-3.5.3.jar:org/apache/maven/messages/build. > > properties(buildNumber): > > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297 > > > > Files that are present in the source distribution but not in the source > > revision: > > DEPENDENCIES > > >
Re: [VOTE] Release Apache Maven 3.5.3
+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: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19 > > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4 > f1c4c96766 > > sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57 > > > > 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 > maven-core-3.5.3.jar:org/apache/maven/messages/build. > properties(buildNumber): > 3383c37e1f9e9b3bc3df5050c29c8aff9f295297 > > Files that are present in the source distribution but not in the source > revision: > DEPENDENCIES >
Re: [VOTE] Release Apache Maven 3.5.3
+1 (non-binding) Testing for ~week with huge OSGi projects. best regards Grzegorz Grzybek 2018-02-28 23:03 GMT+01:00 Robert Scholte: > +1 > > > On Sat, 24 Feb 2018 23:00:28 +0100, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > Hi, >> >> We solved 22 issues: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?versi >> on=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-140 >> 1/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-140 >> 1/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.zip >> https://repository.apache.org/content/repositories/maven-140 >> 1/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-bin.tar.gz >> https://repository.apache.org/content/repositories/maven-140 >> 1/org/apache/maven/apache-maven/3.5.3/apache-maven-3.5.3-src.zip >> https://repository.apache.org/content/repositories/maven-140 >> 1/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: >> 60905d8b8b025b091f456ec25ad60dda56c26ad5 >> sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19 >> apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4 >> f1c4c96766 >> sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57 >> >> 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. >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Apache Maven 3.5.3
+1 On Sat, 24 Feb 2018 23:00:28 +0100, Stephen Connollywrote: 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: 60905d8b8b025b091f456ec25ad60dda56c26ad5 sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19 apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4f1c4c96766 sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57 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. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.5.3
>From my tests looks like a problem with closing PrintStream in JAnsi 1.17. Sylwester wt., 27 lut 2018 o 19:21 użytkownik Guillaume Bouénapisał: > (Made a mistake and only sent this to Stephen... sorry) > > I've found a very small regression, but definitely not a blocker for the > release I think. When the following is ran: > > mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate > > There is a spurious " [0m [0m" at the very last line (note: there are > escape characters before the two square brackets). Doesn't happen with > 3.5.2, the line is empty. (Only tested on Windows). > > Also, I didn't reproduce Dan's issue on Windows with the Takari smart > builder on a single sample project. Maybe the number of modules? > > Guillaume > > > Le 27/02/2018 à 19:01, Dan Tran a écrit : > > Hi all, > > > > I believe my usage of antrun is legit to make sure user who is using mvn > > install ( without clean) has a proper clean up before another plugin > > execution > > > > > > org.apache.maven.plugins > > maven-antrun-plugin > > > > > > > work.around.to.clean.up.classes.before.jsonschema.start > > generate-sources > > > >run > > > > > > > > > > > > > > > > > > > > > > > > here is the command to reproduce the antrun issue > > > > > >mvn clean install --builder smart -T1.0C -DskipTests > > > > > > Add -B to remove the issue but it is not ideal > > > > Only only happens on windows ( i only test with windows and linux) > > > > -D > > > > > > > > On Tue, Feb 27, 2018 at 7:44 AM, Stephen Connolly < > > stephen.alan.conno...@gmail.com> wrote: > > > >> On 27 February 2018 at 14:46, Mirko Friedenhagen < > mfriedenha...@gmail.com> > >> wrote: > >> > >>> +1 from my side, tested with 10 inhouse projects. Or is this vote > >> canceled? > >> Not cancelled yet. Unclear if Dan's issue is something forking maven and > >> parsing the output... the task name > >> "work.around.to.clean.up.classes.before.jsonschema.start" sounds like it > >> could be doing something crazy like that, in which case it is not using > -B > >> when forking maven in Dan's codebase that could be the root cause. > >> > >> > >>> Regards Mirko > >>> -- > >>> http://illegalstateexception.blogspot.com/ > >>> https://github.com/mfriedenhagen/ > >>> https://bitbucket.org/mfriedenhagen/ > >>> > >>> > >>> On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran wrote: > correction > > found this reference, found on 3.5.2 but I only encounter this on > 3.5.3 > >>> RC > https://stackoverflow.com/questions/48723899/maven- > numberformatexception-when-packaging > > > On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran wrote: > > > found this reference, found on 3.5.2 but I only encounter this on > >> 3.5.2 > >>> RC > > https://stackoverflow.com/questions/48723899/maven- > > numberformatexception-when-packaging > > > > On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran > wrote: > > > >> my build contains 270+ modules using java 8. The failure found on > >> windows. Have not tested on Linux yet > >> > >> -D > >> > >> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran > >> wrote: > >>> Encounter random failure at antrun MOJO + smart builder > >>> > >>> here is the error message > >>> > >>> [ERROR] Failed to execute goal org.apache.maven.plugins: > >>> maven-antrun-plugin:1.8:run > >>> (work.around.to.clean.up.classes.before.jsonschema.start) on > >> project > >>> adm-schema: Error executing Ant tasks: For input string: "1;" -> > >>> [Help 1] > >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > >>> execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run > >>> (work.around.to.clean.up.classes.before.jsonschema.start) on > >> project > >>> adm-schema: Error executing Ant tasks: For input string: "1;" > >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute > >>> (MojoExecutor.java:213) > >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute > >>> (MojoExecutor.java:154) > >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute > >>> (MojoExecutor.java:146) > >>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. > >>> buildProject > >>> (LifecycleModuleBuilder.java:117) > >>> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject > >>> (SmartBuilderImpl.java:205) > >>> at io.takari.maven.builder.smart.SmartBuilderImpl$ > >>> ProjectBuildTask.run > >>> (SmartBuilderImpl.java:77) > >>> at java.util.concurrent.Executors$RunnableAdapter.call > >>> (Executors.java:511) > >>> at
Re: [VOTE] Release Apache Maven 3.5.3
+1 No problem found on my side (but light tests) On Tue, Feb 27, 2018 at 10:31 PM, Olivier Lamywrote: > +1 > Thanks to take care of this release! > > > On Wed, 28 Feb 2018 at 7:03 am, Guillaume Boué wrote: > > > +1 > > > > Can make a JIRA for this after the release. > > > > > > Le 27/02/2018 à 19:21, Guillaume Boué a écrit : > > > (Made a mistake and only sent this to Stephen... sorry) > > > > > > I've found a very small regression, but definitely not a blocker for > > > the release I think. When the following is ran: > > > > > > mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate > > > > > > There is a spurious " [0m [0m" at the very last line (note: there are > > > escape characters before the two square brackets). Doesn't happen with > > > 3.5.2, the line is empty. (Only tested on Windows). > > > > > > Also, I didn't reproduce Dan's issue on Windows with the Takari smart > > > builder on a single sample project. Maybe the number of modules? > > > > > > Guillaume > > > > > > > > > Le 27/02/2018 à 19:01, Dan Tran a écrit : > > >> Hi all, > > >> > > >> I believe my usage of antrun is legit to make sure user who is using > > >> mvn > > >> install ( without clean) has a proper clean up before another plugin > > >> execution > > >> > > >> > > >> org.apache.maven.plugins > > >> maven-antrun-plugin > > >> > > >> > > >> work.around.to.clean.up.classes.before.jsonschema.start > > >> generate-sources > > >> > > >>run > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> here is the command to reproduce the antrun issue > > >> > > >> > > >>mvn clean install --builder smart -T1.0C -DskipTests > > >> > > >> > > >> Add -B to remove the issue but it is not ideal > > >> > > >> Only only happens on windows ( i only test with windows and linux) > > >> > > >> -D > > >> > > >> > > >> > > >> On Tue, Feb 27, 2018 at 7:44 AM, Stephen Connolly < > > >> stephen.alan.conno...@gmail.com> wrote: > > >> > > >>> On 27 February 2018 at 14:46, Mirko Friedenhagen > > >>> > > >>> wrote: > > >>> > > +1 from my side, tested with 10 inhouse projects. Or is this vote > > >>> canceled? > > >>> Not cancelled yet. Unclear if Dan's issue is something forking maven > > >>> and > > >>> parsing the output... the task name > > >>> "work.around.to.clean.up.classes.before.jsonschema.start" sounds > > >>> like it > > >>> could be doing something crazy like that, in which case it is not > > >>> using -B > > >>> when forking maven in Dan's codebase that could be the root cause. > > >>> > > >>> > > Regards Mirko > > -- > > http://illegalstateexception.blogspot.com/ > > https://github.com/mfriedenhagen/ > > https://bitbucket.org/mfriedenhagen/ > > > > > > On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran > wrote: > > >correction > > > > > > found this reference, found on 3.5.2 but I only encounter this on > > > 3.5.3 > > RC > > > https://stackoverflow.com/questions/48723899/maven- > > > numberformatexception-when-packaging > > > > > > > > > On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran > wrote: > > > > > >> found this reference, found on 3.5.2 but I only encounter this on > > >>> 3.5.2 > > RC > > >> https://stackoverflow.com/questions/48723899/maven- > > >> numberformatexception-when-packaging > > >> > > >> On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran > > >> wrote: > > >> > > >>> my build contains 270+ modules using java 8. The failure found > on > > >>> windows. Have not tested on Linux yet > > >>> > > >>> -D > > >>> > > >>> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran > > >>> wrote: > > Encounter random failure at antrun MOJO + smart builder > > > > here is the error message > > > > [ERROR] Failed to execute goal org.apache.maven.plugins: > > maven-antrun-plugin:1.8:run > > (work.around.to.clean.up.classes.before.jsonschema.start) on > > >>> project > > adm-schema: Error executing Ant tasks: For input string: "1;" -> > > [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed > to > > execute goal org.apache.maven.plugins: > maven-antrun-plugin:1.8:run > > (work.around.to.clean.up.classes.before.jsonschema.start) on > > >>> project > > adm-schema: Error executing Ant tasks: For input string: "1;" > > at org.apache.maven.lifecycle. > internal.MojoExecutor.execute > > (MojoExecutor.java:213) > > at org.apache.maven.lifecycle. > internal.MojoExecutor.execute >
Re: [VOTE] Release Apache Maven 3.5.3
+1 Thanks to take care of this release! On Wed, 28 Feb 2018 at 7:03 am, Guillaume Bouéwrote: > +1 > > Can make a JIRA for this after the release. > > > Le 27/02/2018 à 19:21, Guillaume Boué a écrit : > > (Made a mistake and only sent this to Stephen... sorry) > > > > I've found a very small regression, but definitely not a blocker for > > the release I think. When the following is ran: > > > > mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate > > > > There is a spurious " [0m [0m" at the very last line (note: there are > > escape characters before the two square brackets). Doesn't happen with > > 3.5.2, the line is empty. (Only tested on Windows). > > > > Also, I didn't reproduce Dan's issue on Windows with the Takari smart > > builder on a single sample project. Maybe the number of modules? > > > > Guillaume > > > > > > Le 27/02/2018 à 19:01, Dan Tran a écrit : > >> Hi all, > >> > >> I believe my usage of antrun is legit to make sure user who is using > >> mvn > >> install ( without clean) has a proper clean up before another plugin > >> execution > >> > >> > >> org.apache.maven.plugins > >> maven-antrun-plugin > >> > >> > >> work.around.to.clean.up.classes.before.jsonschema.start > >> generate-sources > >> > >>run > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> here is the command to reproduce the antrun issue > >> > >> > >>mvn clean install --builder smart -T1.0C -DskipTests > >> > >> > >> Add -B to remove the issue but it is not ideal > >> > >> Only only happens on windows ( i only test with windows and linux) > >> > >> -D > >> > >> > >> > >> On Tue, Feb 27, 2018 at 7:44 AM, Stephen Connolly < > >> stephen.alan.conno...@gmail.com> wrote: > >> > >>> On 27 February 2018 at 14:46, Mirko Friedenhagen > >>> > >>> wrote: > >>> > +1 from my side, tested with 10 inhouse projects. Or is this vote > >>> canceled? > >>> Not cancelled yet. Unclear if Dan's issue is something forking maven > >>> and > >>> parsing the output... the task name > >>> "work.around.to.clean.up.classes.before.jsonschema.start" sounds > >>> like it > >>> could be doing something crazy like that, in which case it is not > >>> using -B > >>> when forking maven in Dan's codebase that could be the root cause. > >>> > >>> > Regards Mirko > -- > http://illegalstateexception.blogspot.com/ > https://github.com/mfriedenhagen/ > https://bitbucket.org/mfriedenhagen/ > > > On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran wrote: > >correction > > > > found this reference, found on 3.5.2 but I only encounter this on > > 3.5.3 > RC > > https://stackoverflow.com/questions/48723899/maven- > > numberformatexception-when-packaging > > > > > > On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran wrote: > > > >> found this reference, found on 3.5.2 but I only encounter this on > >>> 3.5.2 > RC > >> https://stackoverflow.com/questions/48723899/maven- > >> numberformatexception-when-packaging > >> > >> On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran > >> wrote: > >> > >>> my build contains 270+ modules using java 8. The failure found on > >>> windows. Have not tested on Linux yet > >>> > >>> -D > >>> > >>> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran > >>> wrote: > Encounter random failure at antrun MOJO + smart builder > > here is the error message > > [ERROR] Failed to execute goal org.apache.maven.plugins: > maven-antrun-plugin:1.8:run > (work.around.to.clean.up.classes.before.jsonschema.start) on > >>> project > adm-schema: Error executing Ant tasks: For input string: "1;" -> > [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run > (work.around.to.clean.up.classes.before.jsonschema.start) on > >>> project > adm-schema: Error executing Ant tasks: For input string: "1;" > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:213) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. > buildProject > (LifecycleModuleBuilder.java:117) > at > io.takari.maven.builder.smart.SmartBuilderImpl.buildProject >
Re: [VOTE] Release Apache Maven 3.5.3
+1 Can make a JIRA for this after the release. Le 27/02/2018 à 19:21, Guillaume Boué a écrit : (Made a mistake and only sent this to Stephen... sorry) I've found a very small regression, but definitely not a blocker for the release I think. When the following is ran: mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate There is a spurious "[0m[0m" at the very last line (note: there are escape characters before the two square brackets). Doesn't happen with 3.5.2, the line is empty. (Only tested on Windows). Also, I didn't reproduce Dan's issue on Windows with the Takari smart builder on a single sample project. Maybe the number of modules? Guillaume Le 27/02/2018 à 19:01, Dan Tran a écrit : Hi all, I believe my usage of antrun is legit to make sure user who is using mvn install ( without clean) has a proper clean up before another plugin execution org.apache.maven.plugins maven-antrun-plugin work.around.to.clean.up.classes.before.jsonschema.start generate-sources run here is the command to reproduce the antrun issue mvn clean install --builder smart -T1.0C -DskipTests Add -B to remove the issue but it is not ideal Only only happens on windows ( i only test with windows and linux) -D On Tue, Feb 27, 2018 at 7:44 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: On 27 February 2018 at 14:46, Mirko Friedenhagenwrote: +1 from my side, tested with 10 inhouse projects. Or is this vote canceled? Not cancelled yet. Unclear if Dan's issue is something forking maven and parsing the output... the task name "work.around.to.clean.up.classes.before.jsonschema.start" sounds like it could be doing something crazy like that, in which case it is not using -B when forking maven in Dan's codebase that could be the root cause. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran wrote: correction found this reference, found on 3.5.2 but I only encounter this on 3.5.3 RC https://stackoverflow.com/questions/48723899/maven- numberformatexception-when-packaging On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran wrote: found this reference, found on 3.5.2 but I only encounter this on 3.5.2 RC https://stackoverflow.com/questions/48723899/maven- numberformatexception-when-packaging On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran wrote: my build contains 270+ modules using java 8. The failure found on windows. Have not tested on Linux yet -D On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran wrote: Encounter random failure at antrun MOJO + smart builder here is the error message [ERROR] Failed to execute goal org.apache.maven.plugins: maven-antrun-plugin:1.8:run (work.around.to.clean.up.classes.before.jsonschema.start) on project adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (work.around.to.clean.up.classes.before.jsonschema.start) on project adm-schema: Error executing Ant tasks: For input string: "1;" at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. buildProject (LifecycleModuleBuilder.java:117) at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject (SmartBuilderImpl.java:205) at io.takari.maven.builder.smart.SmartBuilderImpl$ ProjectBuildTask.run (SmartBuilderImpl.java:77) at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing Ant tasks: For input string: "1;" at org.apache.maven.plugin.antrun.AntRunMojo.execute (AntRunMojo.java:347) at org.apache.maven.plugin.DefaultBuildPluginManager. executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at
Fwd: [VOTE] Release Apache Maven 3.5.3
Sent from my iPhone Begin forwarded message: > From: Guillaume Boué <gb...@apache.org> > Date: 27 February 2018 at 18:00:29 GMT > To: Stephen Connolly <stephen.alan.conno...@gmail.com> > Subject: Re: [VOTE] Release Apache Maven 3.5.3 > > I've found a very small regression, but definitely not a blocker for the > release I think. When the following is ran: > > mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate > > There is a spurious "[0m[0m" at the very last line (note: there are escape > characters before the two square brackets). Doesn't happen with 3.5.2, the > line is empty. (Only tested on Windows) > > >> Le 27/02/2018 à 16:44, Stephen Connolly a écrit : >> On 27 February 2018 at 14:46, Mirko Friedenhagen <mfriedenha...@gmail.com> >> wrote: >> >>> +1 from my side, tested with 10 inhouse projects. Or is this vote canceled? >>> >> Not cancelled yet. Unclear if Dan's issue is something forking maven and >> parsing the output... the task name >> "work.around.to.clean.up.classes.before.jsonschema.start" sounds like it >> could be doing something crazy like that, in which case it is not using -B >> when forking maven in Dan's codebase that could be the root cause. >> >> >>> Regards Mirko >>> -- >>> http://illegalstateexception.blogspot.com/ >>> https://github.com/mfriedenhagen/ >>> https://bitbucket.org/mfriedenhagen/ >>> >>> >>>> On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran <dant...@gmail.com> wrote: >>>> correction >>>> >>>> found this reference, found on 3.5.2 but I only encounter this on 3.5.3 >>> RC >>>> https://stackoverflow.com/questions/48723899/maven- >>>> numberformatexception-when-packaging >>>> >>>> >>>>> On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran <dant...@gmail.com> wrote: >>>>> >>>>> found this reference, found on 3.5.2 but I only encounter this on 3.5.2 >>> RC >>>>> https://stackoverflow.com/questions/48723899/maven- >>>>> numberformatexception-when-packaging >>>>> >>>>>> On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran <dant...@gmail.com> wrote: >>>>>> >>>>>> my build contains 270+ modules using java 8. The failure found on >>>>>> windows. Have not tested on Linux yet >>>>>> >>>>>> -D >>>>>> >>>>>>> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran <dant...@gmail.com> wrote: >>>>>>> >>>>>>> Encounter random failure at antrun MOJO + smart builder >>>>>>> >>>>>>> here is the error message >>>>>>> >>>>>>> [ERROR] Failed to execute goal org.apache.maven.plugins: >>> maven-antrun-plugin:1.8:run >>>>>>> (work.around.to.clean.up.classes.before.jsonschema.start) on project >>>>>>> adm-schema: Error executing Ant tasks: For input string: "1;" -> >>> [Help 1] >>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >>>>>>> execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run >>>>>>> (work.around.to.clean.up.classes.before.jsonschema.start) on project >>>>>>> adm-schema: Error executing Ant tasks: For input string: "1;" >>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>>>> (MojoExecutor.java:213) >>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>>>> (MojoExecutor.java:154) >>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>>>> (MojoExecutor.java:146) >>>>>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. >>> buildProject >>>>>>> (LifecycleModuleBuilder.java:117) >>>>>>> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject >>>>>>> (SmartBuilderImpl.java:205) >>>>>>> at io.takari.maven.builder.smart.SmartBuilderImpl$ >>> ProjectBuildTask.run >>>>>>> (SmartBuilderImpl.java:77) >>>>>>> at java.util.concurrent.Executors$RunnableAdapter.call >>>>>>> (Executors.java:511) >>>>>&g
Re: [VOTE] Release Apache Maven 3.5.3
(Made a mistake and only sent this to Stephen... sorry) I've found a very small regression, but definitely not a blocker for the release I think. When the following is ran: mvn org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate There is a spurious "[0m[0m" at the very last line (note: there are escape characters before the two square brackets). Doesn't happen with 3.5.2, the line is empty. (Only tested on Windows). Also, I didn't reproduce Dan's issue on Windows with the Takari smart builder on a single sample project. Maybe the number of modules? Guillaume Le 27/02/2018 à 19:01, Dan Tran a écrit : Hi all, I believe my usage of antrun is legit to make sure user who is using mvn install ( without clean) has a proper clean up before another plugin execution org.apache.maven.plugins maven-antrun-plugin work.around.to.clean.up.classes.before.jsonschema.start generate-sources run here is the command to reproduce the antrun issue mvn clean install --builder smart -T1.0C -DskipTests Add -B to remove the issue but it is not ideal Only only happens on windows ( i only test with windows and linux) -D On Tue, Feb 27, 2018 at 7:44 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: On 27 February 2018 at 14:46, Mirko Friedenhagenwrote: +1 from my side, tested with 10 inhouse projects. Or is this vote canceled? Not cancelled yet. Unclear if Dan's issue is something forking maven and parsing the output... the task name "work.around.to.clean.up.classes.before.jsonschema.start" sounds like it could be doing something crazy like that, in which case it is not using -B when forking maven in Dan's codebase that could be the root cause. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran wrote: correction found this reference, found on 3.5.2 but I only encounter this on 3.5.3 RC https://stackoverflow.com/questions/48723899/maven- numberformatexception-when-packaging On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran wrote: found this reference, found on 3.5.2 but I only encounter this on 3.5.2 RC https://stackoverflow.com/questions/48723899/maven- numberformatexception-when-packaging On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran wrote: my build contains 270+ modules using java 8. The failure found on windows. Have not tested on Linux yet -D On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran wrote: Encounter random failure at antrun MOJO + smart builder here is the error message [ERROR] Failed to execute goal org.apache.maven.plugins: maven-antrun-plugin:1.8:run (work.around.to.clean.up.classes.before.jsonschema.start) on project adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (work.around.to.clean.up.classes.before.jsonschema.start) on project adm-schema: Error executing Ant tasks: For input string: "1;" at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. buildProject (LifecycleModuleBuilder.java:117) at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject (SmartBuilderImpl.java:205) at io.takari.maven.builder.smart.SmartBuilderImpl$ ProjectBuildTask.run (SmartBuilderImpl.java:77) at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing Ant tasks: For input string: "1;" at org.apache.maven.plugin.antrun.AntRunMojo.execute (AntRunMojo.java:347) at org.apache.maven.plugin.DefaultBuildPluginManager. executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at
Re: [VOTE] Release Apache Maven 3.5.3
Hi all, I believe my usage of antrun is legit to make sure user who is using mvn install ( without clean) has a proper clean up before another plugin execution org.apache.maven.plugins maven-antrun-plugin work.around.to.clean.up.classes.before.jsonschema.start generate-sources run here is the command to reproduce the antrun issue mvn clean install --builder smart -T1.0C -DskipTests Add -B to remove the issue but it is not ideal Only only happens on windows ( i only test with windows and linux) -D On Tue, Feb 27, 2018 at 7:44 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On 27 February 2018 at 14:46, Mirko Friedenhagen> wrote: > > > +1 from my side, tested with 10 inhouse projects. Or is this vote > canceled? > > > > Not cancelled yet. Unclear if Dan's issue is something forking maven and > parsing the output... the task name > "work.around.to.clean.up.classes.before.jsonschema.start" sounds like it > could be doing something crazy like that, in which case it is not using -B > when forking maven in Dan's codebase that could be the root cause. > > > > Regards Mirko > > -- > > http://illegalstateexception.blogspot.com/ > > https://github.com/mfriedenhagen/ > > https://bitbucket.org/mfriedenhagen/ > > > > > > On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran wrote: > > > correction > > > > > > found this reference, found on 3.5.2 but I only encounter this on 3.5.3 > > RC > > > > > > https://stackoverflow.com/questions/48723899/maven- > > > numberformatexception-when-packaging > > > > > > > > > On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran wrote: > > > > > >> found this reference, found on 3.5.2 but I only encounter this on > 3.5.2 > > RC > > >> > > >> https://stackoverflow.com/questions/48723899/maven- > > >> numberformatexception-when-packaging > > >> > > >> On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran wrote: > > >> > > >>> my build contains 270+ modules using java 8. The failure found on > > >>> windows. Have not tested on Linux yet > > >>> > > >>> -D > > >>> > > >>> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran > wrote: > > >>> > > Encounter random failure at antrun MOJO + smart builder > > > > here is the error message > > > > [ERROR] Failed to execute goal org.apache.maven.plugins: > > maven-antrun-plugin:1.8:run > > (work.around.to.clean.up.classes.before.jsonschema.start) on > project > > adm-schema: Error executing Ant tasks: For input string: "1;" -> > > [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > > execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run > > (work.around.to.clean.up.classes.before.jsonschema.start) on > project > > adm-schema: Error executing Ant tasks: For input string: "1;" > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:213) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:154) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:146) > > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. > > buildProject > > (LifecycleModuleBuilder.java:117) > > at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject > > (SmartBuilderImpl.java:205) > > at io.takari.maven.builder.smart.SmartBuilderImpl$ > > ProjectBuildTask.run > > (SmartBuilderImpl.java:77) > > at java.util.concurrent.Executors$RunnableAdapter.call > > (Executors.java:511) > > at java.util.concurrent.FutureTask.run (FutureTask.java:266) > > at java.util.concurrent.ThreadPoolExecutor.runWorker > > (ThreadPoolExecutor.java:1149) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run > > (ThreadPoolExecutor.java:624) > > at java.lang.Thread.run (Thread.java:748) > > Caused by: org.apache.maven.plugin.MojoExecutionException: Error > > executing Ant tasks: For input string: "1;" > > at org.apache.maven.plugin.antrun.AntRunMojo.execute > > (AntRunMojo.java:347) > > at org.apache.maven.plugin.DefaultBuildPluginManager. > executeMojo > > (DefaultBuildPluginManager.java:137) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:208) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:154) > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > > (MojoExecutor.java:146) > > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. > > buildProject > >
Re: [VOTE] Release Apache Maven 3.5.3
On 27 February 2018 at 14:46, Mirko Friedenhagenwrote: > +1 from my side, tested with 10 inhouse projects. Or is this vote canceled? > Not cancelled yet. Unclear if Dan's issue is something forking maven and parsing the output... the task name "work.around.to.clean.up.classes.before.jsonschema.start" sounds like it could be doing something crazy like that, in which case it is not using -B when forking maven in Dan's codebase that could be the root cause. > Regards Mirko > -- > http://illegalstateexception.blogspot.com/ > https://github.com/mfriedenhagen/ > https://bitbucket.org/mfriedenhagen/ > > > On Sun, Feb 25, 2018 at 10:14 AM, Dan Tran wrote: > > correction > > > > found this reference, found on 3.5.2 but I only encounter this on 3.5.3 > RC > > > > https://stackoverflow.com/questions/48723899/maven- > > numberformatexception-when-packaging > > > > > > On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran wrote: > > > >> found this reference, found on 3.5.2 but I only encounter this on 3.5.2 > RC > >> > >> https://stackoverflow.com/questions/48723899/maven- > >> numberformatexception-when-packaging > >> > >> On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran wrote: > >> > >>> my build contains 270+ modules using java 8. The failure found on > >>> windows. Have not tested on Linux yet > >>> > >>> -D > >>> > >>> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran wrote: > >>> > Encounter random failure at antrun MOJO + smart builder > > here is the error message > > [ERROR] Failed to execute goal org.apache.maven.plugins: > maven-antrun-plugin:1.8:run > (work.around.to.clean.up.classes.before.jsonschema.start) on project > adm-schema: Error executing Ant tasks: For input string: "1;" -> > [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run > (work.around.to.clean.up.classes.before.jsonschema.start) on project > adm-schema: Error executing Ant tasks: For input string: "1;" > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:213) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. > buildProject > (LifecycleModuleBuilder.java:117) > at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject > (SmartBuilderImpl.java:205) > at io.takari.maven.builder.smart.SmartBuilderImpl$ > ProjectBuildTask.run > (SmartBuilderImpl.java:77) > at java.util.concurrent.Executors$RunnableAdapter.call > (Executors.java:511) > at java.util.concurrent.FutureTask.run (FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker > (ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run > (ThreadPoolExecutor.java:624) > at java.lang.Thread.run (Thread.java:748) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error > executing Ant tasks: For input string: "1;" > at org.apache.maven.plugin.antrun.AntRunMojo.execute > (AntRunMojo.java:347) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. > buildProject > (LifecycleModuleBuilder.java:117) > at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject > (SmartBuilderImpl.java:205) > at io.takari.maven.builder.smart.SmartBuilderImpl$ > ProjectBuildTask.run > (SmartBuilderImpl.java:77) > at java.util.concurrent.Executors$RunnableAdapter.call > (Executors.java:511) > at java.util.concurrent.FutureTask.run (FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker > (ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run > (ThreadPoolExecutor.java:624) > at java.lang.Thread.run (Thread.java:748) > Caused by: java.lang.NumberFormatException: For input string: "1;" > at java.lang.NumberFormatException.forInputString > (NumberFormatException.java:65) > at java.lang.Integer.parseInt (Integer.java:580) > at java.lang.Integer. (Integer.java:867) > at org.fusesource.jansi.AnsiPrintStream.filter >
Re: [VOTE] Release Apache Maven 3.5.3
Hi, tested with several projects working the last day with it...No issues.. So +1 from me. Kind regards Karl Heinz Marbaise On 24/02/18 23:00, Stephen Connolly 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: 60905d8b8b025b091f456ec25ad60dda56c26ad5 sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19 apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4f1c4c96766 sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57 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. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.5.3
+1 from my side, tested with 10 inhouse projects. Or is this vote canceled? Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Sun, Feb 25, 2018 at 10:14 AM, Dan Tranwrote: > correction > > found this reference, found on 3.5.2 but I only encounter this on 3.5.3 RC > > https://stackoverflow.com/questions/48723899/maven- > numberformatexception-when-packaging > > > On Sun, Feb 25, 2018 at 1:13 AM, Dan Tran wrote: > >> found this reference, found on 3.5.2 but I only encounter this on 3.5.2 RC >> >> https://stackoverflow.com/questions/48723899/maven- >> numberformatexception-when-packaging >> >> On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran wrote: >> >>> my build contains 270+ modules using java 8. The failure found on >>> windows. Have not tested on Linux yet >>> >>> -D >>> >>> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran wrote: >>> Encounter random failure at antrun MOJO + smart builder here is the error message [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (work.around.to.clean.up.classes.before.jsonschema.start) on project adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (work.around.to.clean.up.classes.before.jsonschema.start) on project adm-schema: Error executing Ant tasks: For input string: "1;" at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject (SmartBuilderImpl.java:205) at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run (SmartBuilderImpl.java:77) at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing Ant tasks: For input string: "1;" at org.apache.maven.plugin.antrun.AntRunMojo.execute (AntRunMojo.java:347) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject (SmartBuilderImpl.java:205) at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run (SmartBuilderImpl.java:77) at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) Caused by: java.lang.NumberFormatException: For input string: "1;" at java.lang.NumberFormatException.forInputString (NumberFormatException.java:65) at java.lang.Integer.parseInt (Integer.java:580) at java.lang.Integer. (Integer.java:867) at org.fusesource.jansi.AnsiPrintStream.filter (AnsiPrintStream.java:129) at org.fusesource.jansi.FilterPrintStream.write (FilterPrintStream.java:59) at org.fusesource.jansi.FilterPrintStream.write (FilterPrintStream.java:70) at java.io.PrintStream.write (PrintStream.java:480) at sun.nio.cs.StreamEncoder.writeBytes (StreamEncoder.java:221) at sun.nio.cs.StreamEncoder.implFlushBuffer (StreamEncoder.java:291) at sun.nio.cs.StreamEncoder.flushBuffer (StreamEncoder.java:104) at java.io.OutputStreamWriter.flushBuffer (OutputStreamWriter.java:185) at
Re: [VOTE] Release Apache Maven 3.5.3
correction found this reference, found on 3.5.2 but I only encounter this on 3.5.3 RC https://stackoverflow.com/questions/48723899/maven- numberformatexception-when-packaging On Sun, Feb 25, 2018 at 1:13 AM, Dan Tranwrote: > found this reference, found on 3.5.2 but I only encounter this on 3.5.2 RC > > https://stackoverflow.com/questions/48723899/maven- > numberformatexception-when-packaging > > On Sun, Feb 25, 2018 at 12:53 AM, Dan Tran wrote: > >> my build contains 270+ modules using java 8. The failure found on >> windows. Have not tested on Linux yet >> >> -D >> >> On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran wrote: >> >>> Encounter random failure at antrun MOJO + smart builder >>> >>> here is the error message >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-antrun-plugin:1.8:run >>> (work.around.to.clean.up.classes.before.jsonschema.start) on project >>> adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1] >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >>> execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run >>> (work.around.to.clean.up.classes.before.jsonschema.start) on project >>> adm-schema: Error executing Ant tasks: For input string: "1;" >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>> (MojoExecutor.java:213) >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>> (MojoExecutor.java:154) >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>> (MojoExecutor.java:146) >>> at >>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject >>> (LifecycleModuleBuilder.java:117) >>> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject >>> (SmartBuilderImpl.java:205) >>> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run >>> (SmartBuilderImpl.java:77) >>> at java.util.concurrent.Executors$RunnableAdapter.call >>> (Executors.java:511) >>> at java.util.concurrent.FutureTask.run (FutureTask.java:266) >>> at java.util.concurrent.ThreadPoolExecutor.runWorker >>> (ThreadPoolExecutor.java:1149) >>> at java.util.concurrent.ThreadPoolExecutor$Worker.run >>> (ThreadPoolExecutor.java:624) >>> at java.lang.Thread.run (Thread.java:748) >>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error >>> executing Ant tasks: For input string: "1;" >>> at org.apache.maven.plugin.antrun.AntRunMojo.execute >>> (AntRunMojo.java:347) >>> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo >>> (DefaultBuildPluginManager.java:137) >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>> (MojoExecutor.java:208) >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>> (MojoExecutor.java:154) >>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>> (MojoExecutor.java:146) >>> at >>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject >>> (LifecycleModuleBuilder.java:117) >>> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject >>> (SmartBuilderImpl.java:205) >>> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run >>> (SmartBuilderImpl.java:77) >>> at java.util.concurrent.Executors$RunnableAdapter.call >>> (Executors.java:511) >>> at java.util.concurrent.FutureTask.run (FutureTask.java:266) >>> at java.util.concurrent.ThreadPoolExecutor.runWorker >>> (ThreadPoolExecutor.java:1149) >>> at java.util.concurrent.ThreadPoolExecutor$Worker.run >>> (ThreadPoolExecutor.java:624) >>> at java.lang.Thread.run (Thread.java:748) >>> Caused by: java.lang.NumberFormatException: For input string: "1;" >>> at java.lang.NumberFormatException.forInputString >>> (NumberFormatException.java:65) >>> at java.lang.Integer.parseInt (Integer.java:580) >>> at java.lang.Integer. (Integer.java:867) >>> at org.fusesource.jansi.AnsiPrintStream.filter >>> (AnsiPrintStream.java:129) >>> at org.fusesource.jansi.FilterPrintStream.write >>> (FilterPrintStream.java:59) >>> at org.fusesource.jansi.FilterPrintStream.write >>> (FilterPrintStream.java:70) >>> at java.io.PrintStream.write (PrintStream.java:480) >>> at sun.nio.cs.StreamEncoder.writeBytes (StreamEncoder.java:221) >>> at sun.nio.cs.StreamEncoder.implFlushBuffer (StreamEncoder.java:291) >>> at sun.nio.cs.StreamEncoder.flushBuffer (StreamEncoder.java:104) >>> at java.io.OutputStreamWriter.flushBuffer >>> (OutputStreamWriter.java:185) >>> at java.io.PrintStream.newLine (PrintStream.java:546) >>> at java.io.PrintStream.println (PrintStream.java:807) >>> at org.apache.tools.ant.DefaultLogger.printMessage >>> (DefaultLogger.java:346) >>> at org.apache.tools.ant.DefaultLogger.targetStarted >>> (DefaultLogger.java:218) >>> at org.apache.tools.ant.Project.fireTargetStarted >>> (Project.java:2140) >>> at
Re: [VOTE] Release Apache Maven 3.5.3
found this reference, found on 3.5.2 but I only encounter this on 3.5.2 RC https://stackoverflow.com/questions/48723899/maven-numberformatexception-when-packaging On Sun, Feb 25, 2018 at 12:53 AM, Dan Tranwrote: > my build contains 270+ modules using java 8. The failure found on > windows. Have not tested on Linux yet > > -D > > On Sun, Feb 25, 2018 at 12:23 AM, Dan Tran wrote: > >> Encounter random failure at antrun MOJO + smart builder >> >> here is the error message >> >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-antrun-plugin:1.8:run >> (work.around.to.clean.up.classes.before.jsonschema.start) on project >> adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1] >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >> execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run >> (work.around.to.clean.up.classes.before.jsonschema.start) on project >> adm-schema: Error executing Ant tasks: For input string: "1;" >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:213) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:154) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:146) >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject >> (LifecycleModuleBuilder.java:117) >> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject >> (SmartBuilderImpl.java:205) >> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run >> (SmartBuilderImpl.java:77) >> at java.util.concurrent.Executors$RunnableAdapter.call >> (Executors.java:511) >> at java.util.concurrent.FutureTask.run (FutureTask.java:266) >> at java.util.concurrent.ThreadPoolExecutor.runWorker >> (ThreadPoolExecutor.java:1149) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run >> (ThreadPoolExecutor.java:624) >> at java.lang.Thread.run (Thread.java:748) >> Caused by: org.apache.maven.plugin.MojoExecutionException: Error >> executing Ant tasks: For input string: "1;" >> at org.apache.maven.plugin.antrun.AntRunMojo.execute >> (AntRunMojo.java:347) >> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo >> (DefaultBuildPluginManager.java:137) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:208) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:154) >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:146) >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject >> (LifecycleModuleBuilder.java:117) >> at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject >> (SmartBuilderImpl.java:205) >> at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run >> (SmartBuilderImpl.java:77) >> at java.util.concurrent.Executors$RunnableAdapter.call >> (Executors.java:511) >> at java.util.concurrent.FutureTask.run (FutureTask.java:266) >> at java.util.concurrent.ThreadPoolExecutor.runWorker >> (ThreadPoolExecutor.java:1149) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run >> (ThreadPoolExecutor.java:624) >> at java.lang.Thread.run (Thread.java:748) >> Caused by: java.lang.NumberFormatException: For input string: "1;" >> at java.lang.NumberFormatException.forInputString >> (NumberFormatException.java:65) >> at java.lang.Integer.parseInt (Integer.java:580) >> at java.lang.Integer. (Integer.java:867) >> at org.fusesource.jansi.AnsiPrintStream.filter >> (AnsiPrintStream.java:129) >> at org.fusesource.jansi.FilterPrintStream.write >> (FilterPrintStream.java:59) >> at org.fusesource.jansi.FilterPrintStream.write >> (FilterPrintStream.java:70) >> at java.io.PrintStream.write (PrintStream.java:480) >> at sun.nio.cs.StreamEncoder.writeBytes (StreamEncoder.java:221) >> at sun.nio.cs.StreamEncoder.implFlushBuffer (StreamEncoder.java:291) >> at sun.nio.cs.StreamEncoder.flushBuffer (StreamEncoder.java:104) >> at java.io.OutputStreamWriter.flushBuffer >> (OutputStreamWriter.java:185) >> at java.io.PrintStream.newLine (PrintStream.java:546) >> at java.io.PrintStream.println (PrintStream.java:807) >> at org.apache.tools.ant.DefaultLogger.printMessage >> (DefaultLogger.java:346) >> at org.apache.tools.ant.DefaultLogger.targetStarted >> (DefaultLogger.java:218) >> at org.apache.tools.ant.Project.fireTargetStarted (Project.java:2140) >> at org.apache.tools.ant.Target.performTasks (Target.java:454) >> at org.apache.tools.ant.Project.executeSortedTargets >> (Project.java:1393) >> at org.apache.tools.ant.Project.executeTarget (Project.java:1364) >> at org.apache.maven.plugin.antrun.AntRunMojo.execute >> (AntRunMojo.java:313) >> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo >>
Re: [VOTE] Release Apache Maven 3.5.3
my build contains 270+ modules using java 8. The failure found on windows. Have not tested on Linux yet -D On Sun, Feb 25, 2018 at 12:23 AM, Dan Tranwrote: > Encounter random failure at antrun MOJO + smart builder > > here is the error message > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-antrun-plugin:1.8:run > (work.around.to.clean.up.classes.before.jsonschema.start) on project > adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run > (work.around.to.clean.up.classes.before.jsonschema.start) on project > adm-schema: Error executing Ant tasks: For input string: "1;" > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:213) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject > (SmartBuilderImpl.java:205) > at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run > (SmartBuilderImpl.java:77) > at java.util.concurrent.Executors$RunnableAdapter.call > (Executors.java:511) > at java.util.concurrent.FutureTask.run (FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker > (ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run > (ThreadPoolExecutor.java:624) > at java.lang.Thread.run (Thread.java:748) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error > executing Ant tasks: For input string: "1;" > at org.apache.maven.plugin.antrun.AntRunMojo.execute > (AntRunMojo.java:347) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject > (SmartBuilderImpl.java:205) > at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run > (SmartBuilderImpl.java:77) > at java.util.concurrent.Executors$RunnableAdapter.call > (Executors.java:511) > at java.util.concurrent.FutureTask.run (FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker > (ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run > (ThreadPoolExecutor.java:624) > at java.lang.Thread.run (Thread.java:748) > Caused by: java.lang.NumberFormatException: For input string: "1;" > at java.lang.NumberFormatException.forInputString > (NumberFormatException.java:65) > at java.lang.Integer.parseInt (Integer.java:580) > at java.lang.Integer. (Integer.java:867) > at org.fusesource.jansi.AnsiPrintStream.filter > (AnsiPrintStream.java:129) > at org.fusesource.jansi.FilterPrintStream.write > (FilterPrintStream.java:59) > at org.fusesource.jansi.FilterPrintStream.write > (FilterPrintStream.java:70) > at java.io.PrintStream.write (PrintStream.java:480) > at sun.nio.cs.StreamEncoder.writeBytes (StreamEncoder.java:221) > at sun.nio.cs.StreamEncoder.implFlushBuffer (StreamEncoder.java:291) > at sun.nio.cs.StreamEncoder.flushBuffer (StreamEncoder.java:104) > at java.io.OutputStreamWriter.flushBuffer > (OutputStreamWriter.java:185) > at java.io.PrintStream.newLine (PrintStream.java:546) > at java.io.PrintStream.println (PrintStream.java:807) > at org.apache.tools.ant.DefaultLogger.printMessage > (DefaultLogger.java:346) > at org.apache.tools.ant.DefaultLogger.targetStarted > (DefaultLogger.java:218) > at org.apache.tools.ant.Project.fireTargetStarted (Project.java:2140) > at org.apache.tools.ant.Target.performTasks (Target.java:454) > at org.apache.tools.ant.Project.executeSortedTargets > (Project.java:1393) > at org.apache.tools.ant.Project.executeTarget (Project.java:1364) > at org.apache.maven.plugin.antrun.AntRunMojo.execute > (AntRunMojo.java:313) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:146) > at
Re: [VOTE] Release Apache Maven 3.5.3
Encounter random failure at antrun MOJO + smart builder here is the error message [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (work.around.to.clean.up.classes.before.jsonschema.start) on project adm-schema: Error executing Ant tasks: For input string: "1;" -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (work.around.to.clean.up.classes.before.jsonschema.start) on project adm-schema: Error executing Ant tasks: For input string: "1;" at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject (SmartBuilderImpl.java:205) at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run (SmartBuilderImpl.java:77) at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing Ant tasks: For input string: "1;" at org.apache.maven.plugin.antrun.AntRunMojo.execute (AntRunMojo.java:347) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject (SmartBuilderImpl.java:205) at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run (SmartBuilderImpl.java:77) at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) Caused by: java.lang.NumberFormatException: For input string: "1;" at java.lang.NumberFormatException.forInputString (NumberFormatException.java:65) at java.lang.Integer.parseInt (Integer.java:580) at java.lang.Integer. (Integer.java:867) at org.fusesource.jansi.AnsiPrintStream.filter (AnsiPrintStream.java:129) at org.fusesource.jansi.FilterPrintStream.write (FilterPrintStream.java:59) at org.fusesource.jansi.FilterPrintStream.write (FilterPrintStream.java:70) at java.io.PrintStream.write (PrintStream.java:480) at sun.nio.cs.StreamEncoder.writeBytes (StreamEncoder.java:221) at sun.nio.cs.StreamEncoder.implFlushBuffer (StreamEncoder.java:291) at sun.nio.cs.StreamEncoder.flushBuffer (StreamEncoder.java:104) at java.io.OutputStreamWriter.flushBuffer (OutputStreamWriter.java:185) at java.io.PrintStream.newLine (PrintStream.java:546) at java.io.PrintStream.println (PrintStream.java:807) at org.apache.tools.ant.DefaultLogger.printMessage (DefaultLogger.java:346) at org.apache.tools.ant.DefaultLogger.targetStarted (DefaultLogger.java:218) at org.apache.tools.ant.Project.fireTargetStarted (Project.java:2140) at org.apache.tools.ant.Target.performTasks (Target.java:454) at org.apache.tools.ant.Project.executeSortedTargets (Project.java:1393) at org.apache.tools.ant.Project.executeTarget (Project.java:1364) at org.apache.maven.plugin.antrun.AntRunMojo.execute (AntRunMojo.java:313) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject (SmartBuilderImpl.java:205) at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run (SmartBuilderImpl.java:77) at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511) at
Re: [VOTE] Release Apache Maven 3.5.3
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: 60905d8b8b025b091f456ec25ad60dda56c26ad5 > sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19 > apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4f1c4c96766 > sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57 > > 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 maven-core-3.5.3.jar:org/apache/maven/messages/build.properties(buildNumber): 3383c37e1f9e9b3bc3df5050c29c8aff9f295297 Files that are present in the source distribution but not in the source revision: DEPENDENCIES
[VOTE] Release Apache Maven 3.5.3
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: 60905d8b8b025b091f456ec25ad60dda56c26ad5 sha256: 471748340cdc7f78b0b0c7bdf9e5399738e6721c08e166f59ef400f1dd107e19 apache-maven-3.5.3-src.zip: sha1: a9be51d571165261dfb2e0c8ecc6b4f1c4c96766 sha256: 109ac07fa337e582b8e6741f179e9f09166cae0fc9b3f44d4a35a2a2c7ccbd57 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.