[ANN] Apache Maven JAR Plugin 3.1.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven JAR Plugin Version 3.1.2. https://maven.apache.org/plugins/maven-jar-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-jar-plugin 3.1.2 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-jar-plugin/download.cgi Release Notes Maven JAR Plugin 3.1.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12344629 Bug * [MJAR-259] - Archiving to jar is very slow Improvement: * [MJAR-238] - Allow setting of module main class Enjoy, - The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[RESULT] [VOTE] Retire Maven Artifact Resolution API (Maven2)
Hi, The vote has passed with the following result: +1: Karl Heinz Marbaise, Anders Hammar, Hervé BOUTEMY, Tamás Cservenák, Gabriel Belingueres, Manfred Moser, Bernd Prager, Enrico Olivelli, Guang Chao, Tibor Digana, Sylwester Lachiewicz, Robert Scholte PMC quorum: reached I will continue with the steps required to retire this library. On 8-5-2019 20:25:14, Robert Scholte wrote: Hi, The Apache Maven project consist of about 100 (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. The Maven Artifact Resolution API (maven-artifact-resolver) is a shared component that could be used to easily resolve Maven project dependencies. The last (and only) released version is 1.0 in September 2009.( https://maven.apache.org/shared/maven-artifact-resolver/ [https://maven.apache.org/shared/maven-artifact-resolver/] ). This library should not be confused with Artifact Resolver (maven-resolver), previously known as Aether. As you can see the naming will cause confusion. The library that aims the same goal for Artifact Resolver is another shared component called maven-artifact-transfer (which by now is not just the transfer part or Artifact Resolver, but a bridge for both Sonatype Aether as used in Maven 3.0.x and Eclipse Aether as used in Maven 3.1.x+. This way Maven plugins and extensions can be compatible with any Maven 3 release) I therefore propose that we retire the maven-artifact-resolver. I don't think it makes sense to do a final release. Instead we should update the documentation and the 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...
Re: Concurrency issue while running Maven on Jenkins host
Hello, I suffered from similar symptoms until I adjusted the build to have per-Jenkins-executor MAven cache. So in the end, my Maven configuration in my Jenkins pipeline looks like this: As you can see, I do not use any Jenkins-Maven plugin and Maven is configured by hand. Hope it may help -- Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Build using toolchains version, but run unit tests against various JDKs?
Hi Nick, it is the latter. The simplest solution is to build and test with the same Java version and configure all variants with your CI server, especially if you consider working with multirelease jars ;) Robert On 13-5-2019 12:26:42, Nick Stolwijk wrote: Hello, I found this old mail about running test multiple times with different JDK's. Has there been any work done to make this possible? Or is the best possible solution to use the CI server to run multiple runs with different JDK's, perhaps using toolchain. With regards, Nick Stolwijk ~~~ Try to leave this world a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~ Lord Baden-Powell On Sat, Mar 4, 2017 at 3:31 AM Hervé BOUTEMY wrote: > yes, using the JDK selected by the toolchain plugin was until recently the > intent of toolchain-plugin: help being consistent in every plugin > requiring to > use a JDK that is different from the JRE used to launch Maven > > now that it works as expected, there are new use cases arising where the > toolchain mechanism is not seen any more as a way to easily *consistently* > select a jdk, but to easily switch between multiple JDKs *differently in > some > plugins executions* > > This is not the same use case: the toolchain definition mecanism > (toolchain.xml) is the same, but selection algorithm is different. > > There was already MNG-5755 [1] implemented in Maven 3.3.1 to prepare hooks > in > Maven core and explain some use cases. > Since then, I know some use cases have been implemented but others not > yet: > I'll try to link related issues in plugins that use the feature. > > In your use case, there is one additional issue: you want to run unit > tests > multiple times, each time with a different JDK configuration. > This will require new feature in Surefire plugin, with extra care on > usability > issues to be sure the new configuration can be understood by normal people. > > Currently, there is a lot of work ongoing on Surefire: this new feature > probably won't be first priority, but in the future, why not. > > Regards, > > Hervé > > > [1] https://issues.apache.org/jira/browse/MNG-5755 > > Le vendredi 3 mars 2017, 07:42:45 CET Russell Gold a écrit : > > I am using the toolchains plugin to ensure that the jars are produced > with > > the correct JDK version; however, I want to be able to unit test against > > both that version and later versions. Is there a way to do that? The > > surefire plugin just selects the same version as was used to build. > > > > Thanks, > > Russ > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Build using toolchains version, but run unit tests against various JDKs?
Hello, I found this old mail about running test multiple times with different JDK's. Has there been any work done to make this possible? Or is the best possible solution to use the CI server to run multiple runs with different JDK's, perhaps using toolchain. With regards, Nick Stolwijk ~~~ Try to leave this world a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~ Lord Baden-Powell On Sat, Mar 4, 2017 at 3:31 AM Hervé BOUTEMY wrote: > yes, using the JDK selected by the toolchain plugin was until recently the > intent of toolchain-plugin: help being consistent in every plugin > requiring to > use a JDK that is different from the JRE used to launch Maven > > now that it works as expected, there are new use cases arising where the > toolchain mechanism is not seen any more as a way to easily *consistently* > select a jdk, but to easily switch between multiple JDKs *differently in > some > plugins executions* > > This is not the same use case: the toolchain definition mecanism > (toolchain.xml) is the same, but selection algorithm is different. > > There was already MNG-5755 [1] implemented in Maven 3.3.1 to prepare hooks > in > Maven core and explain some use cases. > Since then, I know some use cases have been implemented but others not > yet: > I'll try to link related issues in plugins that use the feature. > > In your use case, there is one additional issue: you want to run unit > tests > multiple times, each time with a different JDK configuration. > This will require new feature in Surefire plugin, with extra care on > usability > issues to be sure the new configuration can be understood by normal people. > > Currently, there is a lot of work ongoing on Surefire: this new feature > probably won't be first priority, but in the future, why not. > > Regards, > > Hervé > > > [1] https://issues.apache.org/jira/browse/MNG-5755 > > Le vendredi 3 mars 2017, 07:42:45 CET Russell Gold a écrit : > > I am using the toolchains plugin to ensure that the jars are produced > with > > the correct JDK version; however, I want to be able to unit test against > > both that version and later versions. Is there a way to do that? The > > surefire plugin just selects the same version as was used to build. > > > > Thanks, > > Russ > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
