Re: [VOTE] Retire Maven OSGi
+1 Thank you Dirk for checking Enrico Il giorno ven 23 ago 2019 alle ore 20:48 Arnaud Héritier < aherit...@gmail.com> ha scritto: > +1 > > Le ven. 23 août 2019 à 15:17, Robert Scholte a > écrit : > > > Hi, > > > > The Apache Maven project consist of about 90 (sub)projects. Due to the > > small number of volunteers and the huge amount of code to maintain we're > > missing enough space to make real progress on all these projects, > > including our ambitious ideas for the next major version(s) of Maven > > itself. > > To be able to gain more focus we need to criticize the current > > subprojects > > and decide if it is worth maintaining. > > > > https://maven.apache.org/shared/maven-osgi/ describes the main purpose > > in > > one line: Library for Maven-OSGi integration. > > There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December > > 2007 and just one open issue by Stuart McCulloch regarding an unclosed > jar. > > It is unclear to me if this library is still used. The library is based > > on > > just 3 files: interface, default implementation and dedicated exception. > > Either the library is complete or never used anymore. In both cases I see > > no real reason to maintain it. > > > > I therefore propose that we retire the maven-osgi library. > > > > I don't think it makes sense to do a final release. Instead we should > > update the documentation and freeze the codebase. > > > > The process for retiring a plugin is described here: > > https://maven.apache.org/developers/retirement-plan-plugins.html > > [https://maven.apache.org/developers/retirement-plan-plugins.html] > > > > The vote is open for 72 hours. > > [ ] +1 Yes, it's about time > > [ ] -1 No, because... > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- > - > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier >
Re: Releasing Maven 3.6.2
Il giorno ven 23 ago 2019 alle ore 22:55 Michael Osipov ha scritto: > Am 2019-08-22 um 23:42 schrieb Hervé BOUTEMY: > > We have 49 issues closed and nothing remaining open [1] > > > > Any objection to launch the release now? > > I have now scheduled MNG-6695 for inclusion. It has been worked on for > quite a while. > > Is there are no objections, build passes, I will merge this weekend. > +1 please go I am testing current master and I am checking the maven core release procedure in the meantime Enrico > > Michael > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven Project Info Reports Plugin version 3.0.1
Am 2019-08-23 um 21:33 schrieb Michael Osipov: Hi, We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12344828 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MPIR/issues Staging repo: https://repository.apache.org/content/repositories/maven-1528/ https://repository.apache.org/content/repositories/maven-1528/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.1/maven-project-info-reports-plugin-3.0.1-source-release.zip Source release checksum(s): maven-project-info-reports-plugin-3.0.1-source-release.zip sha512: 7145430a6999ed65a886ac503793f0aa9488b6853431c494c3dee6360c05f3db53fe46ff77bd41514002e8c320b0f4623d23b85d3a9373450c90bb713d3e50be Staging site: https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Project Info Reports Plugin version 3.0.1
build passed ok, sha512 matched +1 On Fri, Aug 23, 2019 at 9:33 PM Michael Osipov wrote: > Hi, > > We solved 5 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12344828 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MPIR/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1528/ > > https://repository.apache.org/content/repositories/maven-1528/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.1/maven-project-info-reports-plugin-3.0.1-source-release.zip > > Source release checksum(s): > maven-project-info-reports-plugin-3.0.1-source-release.zip > sha512: > > 7145430a6999ed65a886ac503793f0aa9488b6853431c494c3dee6360c05f3db53fe46ff77bd41514002e8c320b0f4623d23b85d3a9373450c90bb713d3e50be > > Staging site: > > https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Releasing Maven 3.6.2
Am 2019-08-22 um 23:42 schrieb Hervé BOUTEMY: We have 49 issues closed and nothing remaining open [1] Any objection to launch the release now? I have now scheduled MNG-6695 for inclusion. It has been worked on for quite a while. Is there are no objections, build passes, I will merge this weekend. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing Maven 3.6.2
this MNG-6386 issue is supposed to be fixed since Maven 3.5.4 maybe the IT is just flaky, and it's not a 3.6.2 regression: before investigating, please check if the IT fails also with Maven 3.5.4 to 3.6.1, via -DmavenVersion [1] this will define if this is really a showstopper, or just an enhancement to do later Regards, Hervé [1] https://maven.apache.org/core-its/core-it-suite/ Le vendredi 23 août 2019, 11:55:58 CEST Enrico Olivelli a écrit : > I see this test failing on current master, locally on my machine (MacOS), > this is a show stopper... > I will investigate as soon as possible, but today I can't > > [ERROR] Tests run: 821, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: > 1,366.325 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite > > [ERROR] > testitMNG6386UnicodeChars(org.apache.maven.it.MavenITmng6386BaseUriPropertyT > est) Time elapsed: 1.252 s <<< FAILURE! > > junit.framework.AssertionFailedError > > at > org.apache.maven.it.MavenITmng6386BaseUriPropertyTest.testitMNG6386UnicodeCh > ars(MavenITmng6386BaseUriPropertyTest.java:90) > > > > Enrico > > Il giorno ven 23 ago 2019 alle ore 09:49 Tibor Digana < > > tibordig...@apache.org> ha scritto: > > Yeah Enrico, go for it. ;-) > > Good luck! > > > > T > > > > On Fri, Aug 23, 2019 at 7:18 AM Enrico Olivelli > > > > wrote: > > > Il gio 22 ago 2019, 23:42 Hervé BOUTEMY ha > > > > > > scritto: > > > > We have 49 issues closed and nothing remaining open [1] > > > > > > > > Any objection to launch the release now? > > > > > > > > Any volunteer? > > > > > > I would like to try. I can do it in the weekend. > > > I have only released plugins, maybe I would need some guidance > > > > > > Okay? > > > > > > Enrico > > > > > > > Regards, > > > > > > > > Hervé > > > > > > > > [1] https://issues.apache.org/jira/projects/MNG/versions/12345234 > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Project Info Reports Plugin version 3.0.1
Hi, We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12344828 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MPIR/issues Staging repo: https://repository.apache.org/content/repositories/maven-1528/ https://repository.apache.org/content/repositories/maven-1528/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.1/maven-project-info-reports-plugin-3.0.1-source-release.zip Source release checksum(s): maven-project-info-reports-plugin-3.0.1-source-release.zip sha512: 7145430a6999ed65a886ac503793f0aa9488b6853431c494c3dee6360c05f3db53fe46ff77bd41514002e8c320b0f4623d23b85d3a9373450c90bb713d3e50be Staging site: https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven OSGi
+1 Le ven. 23 août 2019 à 15:17, Robert Scholte a écrit : > Hi, > > The Apache Maven project consist of about 90 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects, > including our ambitious ideas for the next major version(s) of Maven > itself. > To be able to gain more focus we need to criticize the current > subprojects > and decide if it is worth maintaining. > > https://maven.apache.org/shared/maven-osgi/ describes the main purpose > in > one line: Library for Maven-OSGi integration. > There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December > 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar. > It is unclear to me if this library is still used. The library is based > on > just 3 files: interface, default implementation and dedicated exception. > Either the library is complete or never used anymore. In both cases I see > no real reason to maintain it. > > I therefore propose that we retire the maven-osgi library. > > I don't think it makes sense to do a final release. Instead we should > update the documentation and freeze the codebase. > > The process for retiring a plugin is described here: > https://maven.apache.org/developers/retirement-plan-plugins.html > [https://maven.apache.org/developers/retirement-plan-plugins.html] > > The vote is open for 72 hours. > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Retire Maven OSGi
Am 2019-08-23 um 15:17 schrieb Robert Scholte: Hi, The Apache Maven project consist of about 90 (sub)projects. Due to the small number of volunteers and the huge amount of code to maintain we're missing enough space to make real progress on all these projects, including our ambitious ideas for the next major version(s) of Maven itself. To be able to gain more focus we need to criticize the current subprojects and decide if it is worth maintaining. https://maven.apache.org/shared/maven-osgi/ describes the main purpose in one line: Library for Maven-OSGi integration. There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar. It is unclear to me if this library is still used. The library is based on just 3 files: interface, default implementation and dedicated exception. Either the library is complete or never used anymore. In both cases I see no real reason to maintain it. I therefore propose that we retire the maven-osgi library. I don't think it makes sense to do a final release. Instead we should update the documentation and freeze the codebase. The process for retiring a plugin is described here: https://maven.apache.org/developers/retirement-plan-plugins.html [https://maven.apache.org/developers/retirement-plan-plugins.html] +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven OSGi
Hi Dirk, This project is not worth a plugin, it is a pure converter of single class. In this case it is legal to adopt this code according to the license. Anyway the Maven is not the OSGi. The OSGi is not our key API we deliver to our customers. We have to save our energy on what makes Maven The Maven. Cheers Tibor17 On Fri, Aug 23, 2019 at 5:21 PM Dirk Mahler wrote: > Hi, > > I'm not using it but just for curiosity I checked on Maven Central if > some artifacts have been pushed there recently that declare a dependency > to this artifact (maven-osgi): > > "0.2.0" "org.glassfish.hk2:consolidatedbundle-maven-plugin:pom:2.6.0" > "2019-07-31T22:22:29Z" > "0.2.0" "org.glassfish.hk2:osgiversion-maven-plugin:pom:2.6.0" > "2019-07-31T22:21:55Z" > "0.2.0" "org.apache.sling:slingstart-maven-plugin:pom:1.8.4" > "2019-06-13T11:29:18Z" > "0.2.0" "org.apache.sling:slingfeature-maven-plugin:pom:1.0.4" > "2019-06-13T09:52:03Z" > ... > > Hope it helps for voting. > > Cheers > > Dirk > > -- Originalnachricht -- > Von: "Robert Scholte" > An: "Apache Maven Dev" > Cc: "Apache Maven Users" > Gesendet: 23.08.2019 15:17:23 > Betreff: [VOTE] Retire Maven OSGi > > >Hi, > > > >The Apache Maven project consist of about 90 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects, > including our ambitious ideas for the next major version(s) of Maven > itself. > >To be able to gain more focus we need to criticize the current > subprojects and decide if it is worth maintaining. > > > >https://maven.apache.org/shared/maven-osgi/ describes the main purpose > in one line: Library for Maven-OSGi integration. > >There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in > December 2007 and just one open issue by Stuart McCulloch regarding an > unclosed jar. > >It is unclear to me if this library is still used. The library is based > on just 3 files: interface, default implementation and dedicated exception. > >Either the library is complete or never used anymore. In both cases I > see no real reason to maintain it. > > > >I therefore propose that we retire the maven-osgi library. > > > >I don't think it makes sense to do a final release. Instead we should > update the documentation and freeze the codebase. > > > >The process for retiring a plugin is described here: > >https://maven.apache.org/developers/retirement-plan-plugins.html [ > https://maven.apache.org/developers/retirement-plan-plugins.html] > > > >The vote is open for 72 hours. > >[ ] +1 Yes, it's about time > >[ ] -1 No, because... > > > >- > >To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Retire Maven OSGi
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 23.08.19 15:17, Robert Scholte wrote: Hi, The Apache Maven project consist of about 90 (sub)projects. Due to the small number of volunteers and the huge amount of code to maintain we're missing enough space to make real progress on all these projects, including our ambitious ideas for the next major version(s) of Maven itself. To be able to gain more focus we need to criticize the current subprojects and decide if it is worth maintaining. https://maven.apache.org/shared/maven-osgi/ describes the main purpose in one line: Library for Maven-OSGi integration. There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar. It is unclear to me if this library is still used. The library is based on just 3 files: interface, default implementation and dedicated exception. Either the library is complete or never used anymore. In both cases I see no real reason to maintain it. I therefore propose that we retire the maven-osgi library. I don't think it makes sense to do a final release. Instead we should update the documentation and freeze the codebase. The process for retiring a plugin is described here: https://maven.apache.org/developers/retirement-plan-plugins.html [https://maven.apache.org/developers/retirement-plan-plugins.html] The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven OSGi
Hi, I'm not using it but just for curiosity I checked on Maven Central if some artifacts have been pushed there recently that declare a dependency to this artifact (maven-osgi): "0.2.0" "org.glassfish.hk2:consolidatedbundle-maven-plugin:pom:2.6.0" "2019-07-31T22:22:29Z" "0.2.0" "org.glassfish.hk2:osgiversion-maven-plugin:pom:2.6.0" "2019-07-31T22:21:55Z" "0.2.0" "org.apache.sling:slingstart-maven-plugin:pom:1.8.4" "2019-06-13T11:29:18Z" "0.2.0" "org.apache.sling:slingfeature-maven-plugin:pom:1.0.4" "2019-06-13T09:52:03Z" ... Hope it helps for voting. Cheers Dirk -- Originalnachricht -- Von: "Robert Scholte" An: "Apache Maven Dev" Cc: "Apache Maven Users" Gesendet: 23.08.2019 15:17:23 Betreff: [VOTE] Retire Maven OSGi Hi, The Apache Maven project consist of about 90 (sub)projects. Due to the small number of volunteers and the huge amount of code to maintain we're missing enough space to make real progress on all these projects, including our ambitious ideas for the next major version(s) of Maven itself. To be able to gain more focus we need to criticize the current subprojects and decide if it is worth maintaining. https://maven.apache.org/shared/maven-osgi/ describes the main purpose in one line: Library for Maven-OSGi integration. There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar. It is unclear to me if this library is still used. The library is based on just 3 files: interface, default implementation and dedicated exception. Either the library is complete or never used anymore. In both cases I see no real reason to maintain it. I therefore propose that we retire the maven-osgi library. I don't think it makes sense to do a final release. Instead we should update the documentation and freeze the codebase. The process for retiring a plugin is described here: https://maven.apache.org/developers/retirement-plan-plugins.html [https://maven.apache.org/developers/retirement-plan-plugins.html] The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven OSGi
There's very good BND plugin org.apache.felix:maven-bundle-plugin. +1 to retire and delete old https://maven.apache.org/shared/maven-osgi/ Cheers Tibor17 On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte wrote: > Hi, > > The Apache Maven project consist of about 90 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects, > including our ambitious ideas for the next major version(s) of Maven > itself. > To be able to gain more focus we need to criticize the current > subprojects > and decide if it is worth maintaining. > > https://maven.apache.org/shared/maven-osgi/ describes the main purpose > in > one line: Library for Maven-OSGi integration. > There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December > 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar. > It is unclear to me if this library is still used. The library is based > on > just 3 files: interface, default implementation and dedicated exception. > Either the library is complete or never used anymore. In both cases I see > no real reason to maintain it. > > I therefore propose that we retire the maven-osgi library. > > I don't think it makes sense to do a final release. Instead we should > update the documentation and freeze the codebase. > > The process for retiring a plugin is described here: > https://maven.apache.org/developers/retirement-plan-plugins.html > [https://maven.apache.org/developers/retirement-plan-plugins.html] > > The vote is open for 72 hours. > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Retire Maven OSGi
+1 /Anders (mobile) Den fre 23 aug. 2019 15:17Robert Scholte skrev: > Hi, > > The Apache Maven project consist of about 90 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects, > including our ambitious ideas for the next major version(s) of Maven > itself. > To be able to gain more focus we need to criticize the current > subprojects > and decide if it is worth maintaining. > > https://maven.apache.org/shared/maven-osgi/ describes the main purpose > in > one line: Library for Maven-OSGi integration. > There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December > 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar. > It is unclear to me if this library is still used. The library is based > on > just 3 files: interface, default implementation and dedicated exception. > Either the library is complete or never used anymore. In both cases I see > no real reason to maintain it. > > I therefore propose that we retire the maven-osgi library. > > I don't think it makes sense to do a final release. Instead we should > update the documentation and freeze the codebase. > > The process for retiring a plugin is described here: > https://maven.apache.org/developers/retirement-plan-plugins.html > [https://maven.apache.org/developers/retirement-plan-plugins.html] > > The vote is open for 72 hours. > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Retire Maven OSGi
+1 On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte wrote: > Hi, > > The Apache Maven project consist of about 90 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects, > including our ambitious ideas for the next major version(s) of Maven > itself. > To be able to gain more focus we need to criticize the current > subprojects > and decide if it is worth maintaining. > > https://maven.apache.org/shared/maven-osgi/ describes the main purpose > in > one line: Library for Maven-OSGi integration. > There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December > 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar. > It is unclear to me if this library is still used. The library is based > on > just 3 files: interface, default implementation and dedicated exception. > Either the library is complete or never used anymore. In both cases I see > no real reason to maintain it. > > I therefore propose that we retire the maven-osgi library. > > I don't think it makes sense to do a final release. Instead we should > update the documentation and freeze the codebase. > > The process for retiring a plugin is described here: > https://maven.apache.org/developers/retirement-plan-plugins.html > [https://maven.apache.org/developers/retirement-plan-plugins.html] > > The vote is open for 72 hours. > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
[VOTE] Retire Maven OSGi
Hi, The Apache Maven project consist of about 90 (sub)projects. Due to the small number of volunteers and the huge amount of code to maintain we're missing enough space to make real progress on all these projects, including our ambitious ideas for the next major version(s) of Maven itself. To be able to gain more focus we need to criticize the current subprojects and decide if it is worth maintaining. https://maven.apache.org/shared/maven-osgi/ describes the main purpose in one line: Library for Maven-OSGi integration. There have been only 2 releases: 0.1.0 in July 2007 and 0.2.0 in December 2007 and just one open issue by Stuart McCulloch regarding an unclosed jar. It is unclear to me if this library is still used. The library is based on just 3 files: interface, default implementation and dedicated exception. Either the library is complete or never used anymore. In both cases I see no real reason to maintain it. I therefore propose that we retire the maven-osgi library. I don't think it makes sense to do a final release. Instead we should update the documentation and freeze the codebase. The process for retiring a plugin is described here: https://maven.apache.org/developers/retirement-plan-plugins.html [https://maven.apache.org/developers/retirement-plan-plugins.html] The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing Maven 3.6.2
I see this test failing on current master, locally on my machine (MacOS), this is a show stopper... I will investigate as soon as possible, but today I can't [ERROR] Tests run: 821, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1,366.325 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite [ERROR] testitMNG6386UnicodeChars(org.apache.maven.it.MavenITmng6386BaseUriPropertyTest) Time elapsed: 1.252 s <<< FAILURE! junit.framework.AssertionFailedError at org.apache.maven.it.MavenITmng6386BaseUriPropertyTest.testitMNG6386UnicodeChars(MavenITmng6386BaseUriPropertyTest.java:90) Enrico Il giorno ven 23 ago 2019 alle ore 09:49 Tibor Digana < tibordig...@apache.org> ha scritto: > Yeah Enrico, go for it. ;-) > Good luck! > > T > > On Fri, Aug 23, 2019 at 7:18 AM Enrico Olivelli > wrote: > > > Il gio 22 ago 2019, 23:42 Hervé BOUTEMY ha > > scritto: > > > > > We have 49 issues closed and nothing remaining open [1] > > > > > > Any objection to launch the release now? > > > > > > Any volunteer? > > > > > > > I would like to try. I can do it in the weekend. > > I have only released plugins, maybe I would need some guidance > > > > Okay? > > > > Enrico > > > > > > > > > Regards, > > > > > > Hervé > > > > > > [1] https://issues.apache.org/jira/projects/MNG/versions/12345234 > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > >
Re: Releasing Maven 3.6.2
Yeah Enrico, go for it. ;-) Good luck! T On Fri, Aug 23, 2019 at 7:18 AM Enrico Olivelli wrote: > Il gio 22 ago 2019, 23:42 Hervé BOUTEMY ha > scritto: > > > We have 49 issues closed and nothing remaining open [1] > > > > Any objection to launch the release now? > > > > Any volunteer? > > > > I would like to try. I can do it in the weekend. > I have only released plugins, maybe I would need some guidance > > Okay? > > Enrico > > > > > Regards, > > > > Hervé > > > > [1] https://issues.apache.org/jira/projects/MNG/versions/12345234 > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
Re: Surefire CNFE
Thx Romain. My gmail really did not show me the begin of this thread. Now in the mail-archive.apache.org i see that it was related to Dejan's work. The work is still in progress and we have some issues with CNFE which is still okay. For all, currently "surefire-junit4" is activated by default if e.g.junit:junit:4.12 appears in test dependencies. Here in Dejan's change, we attempt to make "surefire-junit47" activated as default Provider for libraries JUnit 4.7+. It is a little upgrade regarding JUnit4.x after years. We know that the feature "re-run" works other way in both providers and this has to be well documented for the users. It would not affect other providers, namely JUnit5, JUnit3 and TestNG. On Fri, Aug 23, 2019 at 6:47 AM Romain Manni-Bucau wrote: > Hi Martin, > > Here it is fully unrelated but more a setup issue, see previous Tibor's > answer. > > @Tibor: topic was changed do your mailbox didnt see the trick but thread is > available at > https://mail-archives.apache.org/mod_mbox/maven-dev/201908.mbox/browser > > > Le ven. 23 août 2019 à 00:45, Tibor Digana a > écrit : > > > I don't know what Jira issue you are refferring to. > > The ICL is used due to user's filtering and the multiple fork VMs. > > > > On Fri, Aug 23, 2019 at 12:40 AM Martin Gainty > > wrote: > > > > > CNFE when running surefire means > > > Isolated (TEST) Classloader cannot load the dependency containing that > > > class > > > In your case that dependency is junit > > > > > > if it was up to me i would discontinue use of Isolated Classloader in > > > favour of using system classloader > > > the only reason Isolated cl was used was the path limitation for System > > > ClassLoader (initially 4k) > > > now all paths including CLASSPATH can be 32k so restricted classpath > > > length should not be an issue > > > > > > ymmv > > > martin- > > > > > > > > > > > >
Re: Releasing Maven 3.6.2
Le vendredi 23 août 2019, 07:45:00 CEST Michael Osipov a écrit : > Am 2019-08-22 um 23:42 schrieb Hervé BOUTEMY: > > We have 49 issues closed and nothing remaining open [1] > > > > Any objection to launch the release now? > > > > Any volunteer? > > > > Regards, > > > > Hervé > > > > [1] https://issues.apache.org/jira/projects/MNG/versions/12345234 > > Tibor wanted to include Resolver 1.4.1 with the offending commit > reverted, but other tickets included. you probably mean https://issues.apache.org/jira/browse/MNG-6738 = 1 of the 49 issues closed - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing Maven 3.6.2
Le vendredi 23 août 2019, 07:17:41 CEST Enrico Olivelli a écrit : > Il gio 22 ago 2019, 23:42 Hervé BOUTEMY ha scritto: > > We have 49 issues closed and nothing remaining open [1] > > > > Any objection to launch the release now? > > > > Any volunteer? > > I would like to try. I can do it in the weekend. > I have only released plugins, maybe I would need some guidance > > Okay? great, thank you I'll be there to help, don't hesitate to ping me > > Enrico > > > Regards, > > > > Hervé > > > > [1] https://issues.apache.org/jira/projects/MNG/versions/12345234 > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
