Typo in my code sample: should be ${tool 'JDK 1.8 (latest)'} as the
lib DSL is something else.
On Mon, 27 Jul 2020 at 10:09, Matt Sicker wrote:
>
> Oh, well, since the tool locations still seem to be the same (they're
> the same nodes after all), hard-coding the JAVA_HOME and PATH+MAVEN
> environ
Oh, well, since the tool locations still seem to be the same (they're
the same nodes after all), hard-coding the JAVA_HOME and PATH+MAVEN
environment variables worked fine. I had initially tried using a
toolchains.xml pointing to all the JDKs installed (well, from 8 to 14
at least) along with using
Hi All,
On Mon, Jul 27, 2020 at 4:48 PM Matt Sicker wrote:
> FYI, the toolchains configFileProvider thing is only needed for
> multi-JDK builds (like in Log4j). The withEnv is the important part
> here.
>
Yes. we have our tool locations in Puppet to popuate the mappings of the
JDKs, Maven
and
FYI, the toolchains configFileProvider thing is only needed for
multi-JDK builds (like in Log4j). The withEnv is the important part
here.
On Mon, 27 Jul 2020 at 09:47, Matt Sicker wrote:
>
> I was unable to get Maven to work using the tool DSL initially, but I
> did manage to get it working with
I was unable to get Maven to work using the tool DSL initially, but I
did manage to get it working with manual PATH setup:
https://github.com/apache/logging-pipelines/blob/master/vars/mvn.groovy
On Mon, 27 Jul 2020 at 05:54, sebb wrote:
>
> What software is installed on the Windows nodes?
>
> I
What software is installed on the Windows nodes?
I was able to find a version of Maven -- 'latest' does not work --
however could not work out how to specify Java for Windows.
This is for https://ci-builds.apache.org/job/Commons/job/commons-net-windows/
On Sat, 25 Jul 2020 at 14:39, Chris Thistle
