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
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
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
--
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 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:
or
