Re: Process maven mdo files via ModelloCLI
I guess no one is familiar with Plexus or Modello. If Maven developers are not familiar with what technologies Maven is built atop. Not sure who else would have a clue about Plexus or Modello. I can look to building Maven via other means. But does not reflect to well on Maven IMHO. Plexus and Modello are part of how Maven is built. Someone should have a clue about both. If your a Maven developer, I highly recommend getting to know Plexus and Modello. It is the underlying foundation to Maven it seems. On Thu, 14 Jun 2018 10:41:14 -0400 "William L. Thomson Jr." wrote: > I have been working on packaging and building Maven from source on > Gentoo. Without using Maven, just straight javac, etc. It is looking > like I cannot do this without using pre-generated sources on Maven > Central. I am having issues with ModelloCLI loading plugins. > https://github.com/codehaus-plexus/modello/issues/15 > > My gut says MetadataPlugins are not the same as Generators. Maybe need > to package more of Modello plugins and/or have them on the classpath. > I am really not clear how Modello loads its plugins via Plexus. Once I > can get the plugin loaded. I should be able to proceed. This is where > I am stuck, Modello loading a plugin to generate Java from mdo files. > I do not need any other formats, just Java. > > Even more interesting, seems to be a chicken/egg situation with parts > of Plexus. Which also has mdo files. > https://github.com/codehaus-plexus/plexus-containers/tree/plexus-containers-1.x/plexus-container-default/src/main/mdo > > Mailing lists for Modello and Plexus seem MIA. It does not seem like > anything else uses this other than Maven. This is not a normal user > issue, thus asking on Maven development list. > > If someone here does not know about Modello and Plexus. Not sure where > I can find someone who does... Thanks for any help! > -- William L. Thomson Jr. pgpwABFa_ZxeO.pgp Description: OpenPGP digital signature
[VOTE] Release Maven Project Info Reports Plugin version 3.0.0
Hi, We solved 24 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12331186 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-1440/ https://repository.apache.org/content/repositories/maven-1440/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.0/maven-project-info-reports-plugin-3.0.0-source-release.zip Source release checksum(s): maven-project-info-reports-plugin-3.0.0-source-release.zip sha1: a5d4f86a7988109791b9ec0d8f76b8df7a24ab3d Staging site: http://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-LATEST/ Guide to testing staged releases: http://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
[ANN] Apache Maven ACR Plugin Version 3.1.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven ACR Plugin Version 3.1.0. This plugin generates J2EE Application Client file. https://maven.apache.org/plugins/maven-acr-plugin/ Important Note: * Maven 3.X only * JDK 7 minimum requirement You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-acr-plugin 3.1.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-acr-plugin/download.cgi Release Notes Maven ACR Plugin 3.1.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317020=12334755 Bugs: * [MACR-41] - Upgrade of plexus-interpolation 1.24 to correct escaping issue. * [MACR-44] - Upgrade mave-surefire/failsafe-plugin 2.21.0 Improvement: * [MACR-30] - Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin Dependency upgrades: * [MACR-28] - Upgrade plexus-archiver from 3.0.1 to 3.0.3 * [MACR-29] - Upgrade plexus-archiver from 3.0.3 to 3.1 * [MACR-31] - Upgrade plexus-archiver from 3.1 to 3.1.1 / maven-archiver from 3.0.0 to 3.0.2 * [MACR-32] - Dependency updates. * [MACR-33] - Upgrade to maven-plugins version 30 * [MACR-34] - Upgrade of 'plexus-archiver' to version 3.3. * [MACR-35] - Upgrade maven-archiver to 3.1.0 * [MACR-36] - Upgrade maven-filtering to 3.1.1 * [MACR-37] - Upgrade plexus-interpolation to 1.22 * [MACR-38] - Upgrade maven-archiver to 3.1.0 * [MACR-39] - Upgrade of plexus-archiver to 3.4. * [MACR-40] - Upgrade of maven-archiver to 3.1.1. * [MACR-42] - Upgrade parent to 31 * [MACR-43] - Upgrade plexus-utils 3.1.0 / maven-archiver / plexus-achiver * [MACR-45] - Upgrade plexus-archiver to 3.6.0 * [MACR-46] - Upgrade plexus-interpolation to 1.25 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Apache Maven ACR Plugin version 3.1.0
Hi, The vote has passed with the following result: +1 : Hervé Boutemy, Robert Scholte, Karl Heinz Marbaise PMC quorum: reached. I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
yes, while at it, the warning on important change will be even more clear Regards, Hervé Le samedi 23 juin 2018, 13:23:43 CEST Karl Heinz Marbaise a écrit : > Hi Hervé, > > On 23/06/18 13:02, Hervé BOUTEMY wrote: > > no misunderstanding: I fully agree with your analysis > > I'm fully +1 > > > > and since Michael will be releasing MPIR soon, with some fixes for JDK > > 9/10 > > support, let's wait for it before releasing Apache parent 20 > > > > go! > > Ah very good ... > > > So we wait for Micheal MPIR release and update MPOM-186 accordingly > afterwards... > > Apart from that... > > WDYT about upgrading maven.compiler.source/target to 1.7 as well ? > > Which I think makes sense ? > > Kind regards > Karl Heinz Marbaise > > > Regards, > > > > Hervé > > > > Le samedi 23 juin 2018, 12:48:37 CEST Karl Heinz Marbaise a écrit : > >> Hi Hervé, > >> > >> On 23/06/18 12:12, Hervé BOUTEMY wrote: > >>> ok; didn't read Karl Heinz email: perfectly explained in MPOM-186, both > >>> what's the expected benefit (JDK 9/10 support) and requirement updates > >>> (minimum JRE 7) > >>> > >>> I don't see any issue with requiring JRE 7 to run Maven: in my last > >>> poll, > >>> the vast majority of people upgraded to Maven 3.5 for color :) , then > >>> have JRE 7 > >>> > >>> We'll just document that change > >> > >> Maybe I misunderstand a thing here. > >> > >> I would suggest to integrate MPOM-186 into ASF Release 20 to get several > >> improvements and updated. > >> > >> MPOM-186 proposes several updates of plugins which is neccessay in > >> particular related to the usage of JDK9/JDK10 and also related to the > >> found issues related to different versions of plugins for our own build > >> (for example surefire 2.20.0 => 2.21.0, JUnit 5 Support of Surefire; > >> JDK10 etc.)..and lifted > >> minimum Java version for running to JRE 7 based also on the upgraded > >> plugins. > >> > >> Furthermore we have fixed several plugins related to possible security > >> issues[1] which should be provided into a new ASF parent pom... > >> > >> > >> Kind regards > >> Karl Heinz Marbaise > >> > >> > >> [1]: http://maven.apache.org/security-plexus-archiver.html > >> > >>> Regards, > >>> > >>> Hervé > >>> > >>> Le samedi 23 juin 2018, 12:06:13 CEST Hervé BOUTEMY a écrit : > I see MPOM-188 was created against maven-parent for that and fixed > > for the moment, priority goes to Apache parent POM > > last call for Apache parent POM updates: there are many plugin updates > available, like compiler 3.7.0, Surefire 2.22 > > Is there a reason not to upgrade? like minium java version? or anything > else? > > Regards, > > Hervé > > Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : > > maven-invoker-plugin doesn't pick up -Dhttps.protocols from the > > JenkinsFile, let's fix this at plugin-parent level > > > > Robert > > > > On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY > > > > > > wrote: > >> Hi, > >> > >> As told in INFRA-16467 thread, I'll do parent POMs releases soon. > >> > >> Please update parent POMs as you want the release to be done: I'll > >> start > >> by Apache parent in a few days: see the diff against Apache 19 [1] > >> and the site https://maven.apache.org/pom-archives/asf-LATEST/ > >> > >> Once Apache parent 20 is released, I'll let a few days for Maven > >> parent > >> POMS > >> > >> Regards, > >> > >> Hervé > >> > >> [1] > >> https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobd > >> if > >> f > >> ;f > >> =pom.xml;hb=master;hpb=apache-19 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
For Java the proposal to include the year in the version has been dropped, it is only there in the description. I don't see any benefit for it for Maven. Our release ratio is quite low, so adding a year might suggest that a specific release it quite old, even though it is the most recent one. With over 90 subprojects in Maven, the semantic versioning schema fits much better. Robert On Sat, 23 Jun 2018 13:42:32 +0200, Sylwester Lachiewicz wrote: hi, what do you think about option to change versioning schema to something like java will follow? ie change to YY.qq.build? with 19 now will be hard but if we release now 19.1 and in next year start with normal cumulative montly/quarter releases for asf/maven pom? Sylwester W dniu sob., 23.06.2018 o 13:23 Karl Heinz Marbaise napisał(a): Hi Hervé, On 23/06/18 13:02, Hervé BOUTEMY wrote: > no misunderstanding: I fully agree with your analysis > I'm fully +1 > > and since Michael will be releasing MPIR soon, with some fixes for JDK 9/10 > support, let's wait for it before releasing Apache parent 20 > > go! Ah very good ... So we wait for Micheal MPIR release and update MPOM-186 accordingly afterwards... Apart from that... WDYT about upgrading maven.compiler.source/target to 1.7 as well ? Which I think makes sense ? Kind regards Karl Heinz Marbaise > > Regards, > > Hervé > > Le samedi 23 juin 2018, 12:48:37 CEST Karl Heinz Marbaise a écrit : >> Hi Hervé, >> >> On 23/06/18 12:12, Hervé BOUTEMY wrote: >>> ok; didn't read Karl Heinz email: perfectly explained in MPOM-186, both >>> what's the expected benefit (JDK 9/10 support) and requirement updates >>> (minimum JRE 7) >>> >>> I don't see any issue with requiring JRE 7 to run Maven: in my last poll, >>> the vast majority of people upgraded to Maven 3.5 for color :) , then >>> have JRE 7 >>> >>> We'll just document that change >> >> Maybe I misunderstand a thing here. >> >> I would suggest to integrate MPOM-186 into ASF Release 20 to get several >> improvements and updated. >> >> MPOM-186 proposes several updates of plugins which is neccessay in >> particular related to the usage of JDK9/JDK10 and also related to the >> found issues related to different versions of plugins for our own build >> (for example surefire 2.20.0 => 2.21.0, JUnit 5 Support of Surefire; >> JDK10 etc.)..and lifted >> minimum Java version for running to JRE 7 based also on the upgraded >> plugins. >> >> Furthermore we have fixed several plugins related to possible security >> issues[1] which should be provided into a new ASF parent pom... >> >> >> Kind regards >> Karl Heinz Marbaise >> >> >> [1]: http://maven.apache.org/security-plexus-archiver.html >> >>> Regards, >>> >>> Hervé >>> >>> Le samedi 23 juin 2018, 12:06:13 CEST Hervé BOUTEMY a écrit : I see MPOM-188 was created against maven-parent for that and fixed for the moment, priority goes to Apache parent POM last call for Apache parent POM updates: there are many plugin updates available, like compiler 3.7.0, Surefire 2.22 Is there a reason not to upgrade? like minium java version? or anything else? Regards, Hervé Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : > maven-invoker-plugin doesn't pick up -Dhttps.protocols from the > JenkinsFile, let's fix this at plugin-parent level > > Robert > > On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY > > > wrote: >> Hi, >> >> As told in INFRA-16467 thread, I'll do parent POMs releases soon. >> >> Please update parent POMs as you want the release to be done: I'll >> start >> by Apache parent in a few days: see the diff against Apache 19 [1] >> and the site https://maven.apache.org/pom-archives/asf-LATEST/ >> >> Once Apache parent 20 is released, I'll let a few days for Maven parent >> POMS >> >> Regards, >> >> Hervé >> >> [1] >> https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobdif >> f >> ;f >> =pom.xml;hb=master;hpb=apache-19 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
hi, what do you think about option to change versioning schema to something like java will follow? ie change to YY.qq.build? with 19 now will be hard but if we release now 19.1 and in next year start with normal cumulative montly/quarter releases for asf/maven pom? Sylwester W dniu sob., 23.06.2018 o 13:23 Karl Heinz Marbaise napisał(a): > Hi Hervé, > > On 23/06/18 13:02, Hervé BOUTEMY wrote: > > no misunderstanding: I fully agree with your analysis > > I'm fully +1 > > > > and since Michael will be releasing MPIR soon, with some fixes for JDK > 9/10 > > support, let's wait for it before releasing Apache parent 20 > > > > go! > > Ah very good ... > > > So we wait for Micheal MPIR release and update MPOM-186 accordingly > afterwards... > > Apart from that... > > WDYT about upgrading maven.compiler.source/target to 1.7 as well ? > > Which I think makes sense ? > > Kind regards > Karl Heinz Marbaise > > > > Regards, > > > > Hervé > > > > Le samedi 23 juin 2018, 12:48:37 CEST Karl Heinz Marbaise a écrit : > >> Hi Hervé, > >> > >> On 23/06/18 12:12, Hervé BOUTEMY wrote: > >>> ok; didn't read Karl Heinz email: perfectly explained in MPOM-186, both > >>> what's the expected benefit (JDK 9/10 support) and requirement updates > >>> (minimum JRE 7) > >>> > >>> I don't see any issue with requiring JRE 7 to run Maven: in my last > poll, > >>> the vast majority of people upgraded to Maven 3.5 for color :) , then > >>> have JRE 7 > >>> > >>> We'll just document that change > >> > >> Maybe I misunderstand a thing here. > >> > >> I would suggest to integrate MPOM-186 into ASF Release 20 to get several > >> improvements and updated. > >> > >> MPOM-186 proposes several updates of plugins which is neccessay in > >> particular related to the usage of JDK9/JDK10 and also related to the > >> found issues related to different versions of plugins for our own build > >> (for example surefire 2.20.0 => 2.21.0, JUnit 5 Support of Surefire; > >> JDK10 etc.)..and lifted > >> minimum Java version for running to JRE 7 based also on the upgraded > >> plugins. > >> > >> Furthermore we have fixed several plugins related to possible security > >> issues[1] which should be provided into a new ASF parent pom... > >> > >> > >> Kind regards > >> Karl Heinz Marbaise > >> > >> > >> [1]: http://maven.apache.org/security-plexus-archiver.html > >> > >>> Regards, > >>> > >>> Hervé > >>> > >>> Le samedi 23 juin 2018, 12:06:13 CEST Hervé BOUTEMY a écrit : > I see MPOM-188 was created against maven-parent for that and fixed > > for the moment, priority goes to Apache parent POM > > last call for Apache parent POM updates: there are many plugin updates > available, like compiler 3.7.0, Surefire 2.22 > > Is there a reason not to upgrade? like minium java version? or > anything > else? > > Regards, > > Hervé > > Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : > > maven-invoker-plugin doesn't pick up -Dhttps.protocols from the > > JenkinsFile, let's fix this at plugin-parent level > > > > Robert > > > > On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY > > > > > > wrote: > >> Hi, > >> > >> As told in INFRA-16467 thread, I'll do parent POMs releases soon. > >> > >> Please update parent POMs as you want the release to be done: I'll > >> start > >> by Apache parent in a few days: see the diff against Apache 19 [1] > >> and the site https://maven.apache.org/pom-archives/asf-LATEST/ > >> > >> Once Apache parent 20 is released, I'll let a few days for Maven > parent > >> POMS > >> > >> Regards, > >> > >> Hervé > >> > >> [1] > >> > https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobdif > >> f > >> ;f > >> =pom.xml;hb=master;hpb=apache-19 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: parent POMS release in a few days
Hi Hervé, On 23/06/18 13:02, Hervé BOUTEMY wrote: no misunderstanding: I fully agree with your analysis I'm fully +1 and since Michael will be releasing MPIR soon, with some fixes for JDK 9/10 support, let's wait for it before releasing Apache parent 20 go! Ah very good ... So we wait for Micheal MPIR release and update MPOM-186 accordingly afterwards... Apart from that... WDYT about upgrading maven.compiler.source/target to 1.7 as well ? Which I think makes sense ? Kind regards Karl Heinz Marbaise Regards, Hervé Le samedi 23 juin 2018, 12:48:37 CEST Karl Heinz Marbaise a écrit : Hi Hervé, On 23/06/18 12:12, Hervé BOUTEMY wrote: ok; didn't read Karl Heinz email: perfectly explained in MPOM-186, both what's the expected benefit (JDK 9/10 support) and requirement updates (minimum JRE 7) I don't see any issue with requiring JRE 7 to run Maven: in my last poll, the vast majority of people upgraded to Maven 3.5 for color :) , then have JRE 7 We'll just document that change Maybe I misunderstand a thing here. I would suggest to integrate MPOM-186 into ASF Release 20 to get several improvements and updated. MPOM-186 proposes several updates of plugins which is neccessay in particular related to the usage of JDK9/JDK10 and also related to the found issues related to different versions of plugins for our own build (for example surefire 2.20.0 => 2.21.0, JUnit 5 Support of Surefire; JDK10 etc.)..and lifted minimum Java version for running to JRE 7 based also on the upgraded plugins. Furthermore we have fixed several plugins related to possible security issues[1] which should be provided into a new ASF parent pom... Kind regards Karl Heinz Marbaise [1]: http://maven.apache.org/security-plexus-archiver.html Regards, Hervé Le samedi 23 juin 2018, 12:06:13 CEST Hervé BOUTEMY a écrit : I see MPOM-188 was created against maven-parent for that and fixed for the moment, priority goes to Apache parent POM last call for Apache parent POM updates: there are many plugin updates available, like compiler 3.7.0, Surefire 2.22 Is there a reason not to upgrade? like minium java version? or anything else? Regards, Hervé Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : maven-invoker-plugin doesn't pick up -Dhttps.protocols from the JenkinsFile, let's fix this at plugin-parent level Robert On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY wrote: Hi, As told in INFRA-16467 thread, I'll do parent POMs releases soon. Please update parent POMs as you want the release to be done: I'll start by Apache parent in a few days: see the diff against Apache 19 [1] and the site https://maven.apache.org/pom-archives/asf-LATEST/ Once Apache parent 20 is released, I'll let a few days for Maven parent POMS Regards, Hervé [1] https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobdif f ;f =pom.xml;hb=master;hpb=apache-19 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [INFRA-16467] move components documentation out of CMS space
Happy that you like it and prefer ignore the few glitches: - killed Jenkins server because of the automated git commits :) - commit emails that should be avoided to commits@maven.a.o but all in all, yes, it worked quite well git the impact of the change Regards, Hervé Le mardi 19 juin 2018, 20:23:11 CEST Karl Heinz Marbaise a écrit : > Hi Hervé, > > On 19/06/18 07:54, Hervé BOUTEMY wrote: > > just tested the full component documentation lifecycle for Maven [1] and > > Doxia [2]: works like a charm > > I can acknowledge that it worked like a charm. > > Great work. > > Thanks. > > Kind regards > Karl Heinz Marbaise > > > *IMPORTANT NOTICE: you'll have to delete your ~/maven-sites cache* > > since the cache contains svn checkouts to the old location, that will be > > updated: you need to delete to make the checkouts recreate to the new > > location > > > > > > Next step is to release parent POMs that contain updated location, to be > > sure relative path calculation when generating or publishing site won't > > be broken by the different roots. > > > > Regards, > > > > Hervé > > > > [1] https://maven.apache.org/pom-archives/asf-LATEST/ > > > > [2] > > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-L > > ATEST/> > > Le mardi 19 juin 2018, 00:32:12 CEST Hervé BOUTEMY a écrit : > >> Hi, > >> > >> As you may have noticed from a load of commits, the location for html > >> publication of components documentation is switching from CMS space to > >> ASF > >> repo, as requested by INFRA when working on site migration from svn to > >> Git. > >> > >> see https://issues.apache.org/jira/browse/INFRA-16467 > >> > >> Please wait a little bit for me to test the new setup before publishing > >> any > >> component documentation (main site can be published, it's a separate > >> configuration) > >> > >> Probably it will be safer to do a parent POM release before doing newer > >> releases: please have a look at parent POMs for updates you want to see > >> in > >> the next release > >> > >> Regards, > >> > >> Hervé - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
no misunderstanding: I fully agree with your analysis I'm fully +1 and since Michael will be releasing MPIR soon, with some fixes for JDK 9/10 support, let's wait for it before releasing Apache parent 20 go! Regards, Hervé Le samedi 23 juin 2018, 12:48:37 CEST Karl Heinz Marbaise a écrit : > Hi Hervé, > > On 23/06/18 12:12, Hervé BOUTEMY wrote: > > ok; didn't read Karl Heinz email: perfectly explained in MPOM-186, both > > what's the expected benefit (JDK 9/10 support) and requirement updates > > (minimum JRE 7) > > > > I don't see any issue with requiring JRE 7 to run Maven: in my last poll, > > the vast majority of people upgraded to Maven 3.5 for color :) , then > > have JRE 7 > > > > We'll just document that change > > Maybe I misunderstand a thing here. > > I would suggest to integrate MPOM-186 into ASF Release 20 to get several > improvements and updated. > > MPOM-186 proposes several updates of plugins which is neccessay in > particular related to the usage of JDK9/JDK10 and also related to the > found issues related to different versions of plugins for our own build > (for example surefire 2.20.0 => 2.21.0, JUnit 5 Support of Surefire; > JDK10 etc.)..and lifted > minimum Java version for running to JRE 7 based also on the upgraded > plugins. > > Furthermore we have fixed several plugins related to possible security > issues[1] which should be provided into a new ASF parent pom... > > > Kind regards > Karl Heinz Marbaise > > > [1]: http://maven.apache.org/security-plexus-archiver.html > > > Regards, > > > > Hervé > > > > Le samedi 23 juin 2018, 12:06:13 CEST Hervé BOUTEMY a écrit : > >> I see MPOM-188 was created against maven-parent for that and fixed > >> > >> for the moment, priority goes to Apache parent POM > >> > >> last call for Apache parent POM updates: there are many plugin updates > >> available, like compiler 3.7.0, Surefire 2.22 > >> > >> Is there a reason not to upgrade? like minium java version? or anything > >> else? > >> > >> Regards, > >> > >> Hervé > >> > >> Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : > >>> maven-invoker-plugin doesn't pick up -Dhttps.protocols from the > >>> JenkinsFile, let's fix this at plugin-parent level > >>> > >>> Robert > >>> > >>> On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY > >>> > >>> > >>> wrote: > Hi, > > As told in INFRA-16467 thread, I'll do parent POMs releases soon. > > Please update parent POMs as you want the release to be done: I'll > start > by Apache parent in a few days: see the diff against Apache 19 [1] > and the site https://maven.apache.org/pom-archives/asf-LATEST/ > > Once Apache parent 20 is released, I'll let a few days for Maven parent > POMS > > Regards, > > Hervé > > [1] > https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobdif > f > ;f > =pom.xml;hb=master;hpb=apache-19 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
Hi Hervé, On 23/06/18 12:12, Hervé BOUTEMY wrote: ok; didn't read Karl Heinz email: perfectly explained in MPOM-186, both what's the expected benefit (JDK 9/10 support) and requirement updates (minimum JRE 7) I don't see any issue with requiring JRE 7 to run Maven: in my last poll, the vast majority of people upgraded to Maven 3.5 for color :) , then have JRE 7 We'll just document that change Maybe I misunderstand a thing here. I would suggest to integrate MPOM-186 into ASF Release 20 to get several improvements and updated. MPOM-186 proposes several updates of plugins which is neccessay in particular related to the usage of JDK9/JDK10 and also related to the found issues related to different versions of plugins for our own build (for example surefire 2.20.0 => 2.21.0, JUnit 5 Support of Surefire; JDK10 etc.)..and lifted minimum Java version for running to JRE 7 based also on the upgraded plugins. Furthermore we have fixed several plugins related to possible security issues[1] which should be provided into a new ASF parent pom... Kind regards Karl Heinz Marbaise [1]: http://maven.apache.org/security-plexus-archiver.html Regards, Hervé Le samedi 23 juin 2018, 12:06:13 CEST Hervé BOUTEMY a écrit : I see MPOM-188 was created against maven-parent for that and fixed for the moment, priority goes to Apache parent POM last call for Apache parent POM updates: there are many plugin updates available, like compiler 3.7.0, Surefire 2.22 Is there a reason not to upgrade? like minium java version? or anything else? Regards, Hervé Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : maven-invoker-plugin doesn't pick up -Dhttps.protocols from the JenkinsFile, let's fix this at plugin-parent level Robert On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY wrote: Hi, As told in INFRA-16467 thread, I'll do parent POMs releases soon. Please update parent POMs as you want the release to be done: I'll start by Apache parent in a few days: see the diff against Apache 19 [1] and the site https://maven.apache.org/pom-archives/asf-LATEST/ Once Apache parent 20 is released, I'll let a few days for Maven parent POMS Regards, Hervé [1] https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobdiff ;f =pom.xml;hb=master;hpb=apache-19 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
Hi, I have created MPOM-186 for ASF ... So you think it would be a good idea to integrate that into ASF parent... Kind regards Karl Heinz Marbaise On 23/06/18 12:10, Karl Heinz Marbaise wrote: Hi Hervé, On 23/06/18 12:06, Hervé BOUTEMY wrote: I see MPOM-188 was created against maven-parent for that and fixed for the moment, priority goes to Apache parent POM last call for Apache parent POM updates: there are many plugin updates available, like compiler 3.7.0, Surefire 2.22 It might be better to make them against ASF Parent pom... Would that be ok from your point of view? Kind regards Karl Heinz Marbaise Is there a reason not to upgrade? like minium java version? or anything else? Regards, Hervé Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : maven-invoker-plugin doesn't pick up -Dhttps.protocols from the JenkinsFile, let's fix this at plugin-parent level Robert On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY wrote: Hi, As told in INFRA-16467 thread, I'll do parent POMs releases soon. Please update parent POMs as you want the release to be done: I'll start by Apache parent in a few days: see the diff against Apache 19 [1] and the site https://maven.apache.org/pom-archives/asf-LATEST/ Once Apache parent 20 is released, I'll let a few days for Maven parent POMS Regards, Hervé [1] https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobdiff;f =pom.xml;hb=master;hpb=apache-19 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
ok; didn't read Karl Heinz email: perfectly explained in MPOM-186, both what's the expected benefit (JDK 9/10 support) and requirement updates (minimum JRE 7) I don't see any issue with requiring JRE 7 to run Maven: in my last poll, the vast majority of people upgraded to Maven 3.5 for color :) , then have JRE 7 We'll just document that change Regards, Hervé Le samedi 23 juin 2018, 12:06:13 CEST Hervé BOUTEMY a écrit : > I see MPOM-188 was created against maven-parent for that and fixed > > for the moment, priority goes to Apache parent POM > > last call for Apache parent POM updates: there are many plugin updates > available, like compiler 3.7.0, Surefire 2.22 > > Is there a reason not to upgrade? like minium java version? or anything > else? > > Regards, > > Hervé > > Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : > > maven-invoker-plugin doesn't pick up -Dhttps.protocols from the > > JenkinsFile, let's fix this at plugin-parent level > > > > Robert > > > > On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY > > > > wrote: > > > Hi, > > > > > > As told in INFRA-16467 thread, I'll do parent POMs releases soon. > > > > > > Please update parent POMs as you want the release to be done: I'll start > > > by Apache parent in a few days: see the diff against Apache 19 [1] > > > and the site https://maven.apache.org/pom-archives/asf-LATEST/ > > > > > > Once Apache parent 20 is released, I'll let a few days for Maven parent > > > POMS > > > > > > Regards, > > > > > > Hervé > > > > > > [1] > > > https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobdiff > > > ;f > > > =pom.xml;hb=master;hpb=apache-19 > > > > > > > > > > > > - > > > 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 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven ACR Plugin version 3.1.0
+1 On Tue, 19 Jun 2018 20:14:09 +0200, Karl Heinz Marbaise wrote: Hi, We solved 19 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317020=12334755 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MACR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1439 https://repository.apache.org/content/repositories/maven-1439/org/apache/maven/plugins/maven-acr-plugin/3.1.0/maven-acr-plugin-3.1.0-source-release.zip Source release checksum(s): maven-acr-plugin-3.1.0-source-release.zip sha1: 1a97ceae42ae12b3cf70130915cdb77b99c251a5 Staging site: https://maven.apache.org/plugins-archives/maven-acr-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
Hi Hervé, On 23/06/18 12:06, Hervé BOUTEMY wrote: I see MPOM-188 was created against maven-parent for that and fixed for the moment, priority goes to Apache parent POM last call for Apache parent POM updates: there are many plugin updates available, like compiler 3.7.0, Surefire 2.22 It might be better to make them against ASF Parent pom... Would that be ok from your point of view? Kind regards Karl Heinz Marbaise Is there a reason not to upgrade? like minium java version? or anything else? Regards, Hervé Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : maven-invoker-plugin doesn't pick up -Dhttps.protocols from the JenkinsFile, let's fix this at plugin-parent level Robert On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY wrote: Hi, As told in INFRA-16467 thread, I'll do parent POMs releases soon. Please update parent POMs as you want the release to be done: I'll start by Apache parent in a few days: see the diff against Apache 19 [1] and the site https://maven.apache.org/pom-archives/asf-LATEST/ Once Apache parent 20 is released, I'll let a few days for Maven parent POMS Regards, Hervé [1] https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobdiff;f =pom.xml;hb=master;hpb=apache-19 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
Am 2018-06-23 um 12:06 schrieb Hervé BOUTEMY: I see MPOM-188 was created against maven-parent for that and fixed for the moment, priority goes to Apache parent POM last call for Apache parent POM updates: there are many plugin updates available, like compiler 3.7.0, Surefire 2.22 I'd like to add MPIR, which I will start voting today. It is upgraded to Maven with long standing issues. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: parent POMS release in a few days
I see MPOM-188 was created against maven-parent for that and fixed for the moment, priority goes to Apache parent POM last call for Apache parent POM updates: there are many plugin updates available, like compiler 3.7.0, Surefire 2.22 Is there a reason not to upgrade? like minium java version? or anything else? Regards, Hervé Le vendredi 22 juin 2018, 20:38:12 CEST Robert Scholte a écrit : > maven-invoker-plugin doesn't pick up -Dhttps.protocols from the > JenkinsFile, let's fix this at plugin-parent level > > Robert > > On Tue, 19 Jun 2018 07:57:25 +0200, Hervé BOUTEMY > > wrote: > > Hi, > > > > As told in INFRA-16467 thread, I'll do parent POMs releases soon. > > > > Please update parent POMs as you want the release to be done: I'll start > > by Apache parent in a few days: see the diff against Apache 19 [1] > > and the site https://maven.apache.org/pom-archives/asf-LATEST/ > > > > Once Apache parent 20 is released, I'll let a few days for Maven parent > > POMS > > > > Regards, > > > > Hervé > > > > [1] > > https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=blobdiff;f > > =pom.xml;hb=master;hpb=apache-19 > > > > > > > > - > > 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven ACR Plugin version 3.1.0
+1 Regards, Hervé Le mardi 19 juin 2018, 20:14:09 CEST Karl Heinz Marbaise a écrit : > Hi, > > We solved 19 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317020 > rsion=12334755 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MACR%20AND%20reso > lution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1439 > https://repository.apache.org/content/repositories/maven-1439/org/apache/mav > en/plugins/maven-acr-plugin/3.1.0/maven-acr-plugin-3.1.0-source-release.zip > > Source release checksum(s): > maven-acr-plugin-3.1.0-source-release.zip sha1: > 1a97ceae42ae12b3cf70130915cdb77b99c251a5 > > Staging site: > https://maven.apache.org/plugins-archives/maven-acr-plugin-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Kind regards > Karl Heinz Marbaise > > - > 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
