pt., 11 paź 2019 o 05:50 Tilman Hausherr <thaush...@t-online.de> napisał(a): > > Sadly it's more complex - the build is started on jdk8 and javac forked > on jdk6. So we need both, and the possibility to access the jdk from > within maven. > > I tried a "pure" jdk6 build on my windows machine and that failed for > several reasons, one of them being the failure of an external download > because IIRC an incompatibility on SSL protocols. That must have neen > the reason we stopped doing a "pure" jdk6 build years ago. > > On my Windows machine, the maven build is started on jdk8 but with > -Djdk.path="C:/Program Files/Java/jdk1.6.0_45" in the command line. > That's why I asked for the directory, obviously the jdk6 won't be in > "/home/jenkins/tools/java/..." in that image.
So you need both JDKs - JDK8 and JDK6? I would go ahead and create my own Docker image starting off the one with JDK6 and Maven, then installing JDK8 - it all can be achieved by a simple Dockerfile and pushing changes to Apache's repo at Docker Hub. In such case you will have a full control of what tools you need and you won't depend on INFRA anymore. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/
