If you don't need jdk auto install then try using maven toolchains.
Then run the job with whatever jdk works for maven and Jenkins
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it
Switching to a freestyle build with a maven build step should resolve the
issue as you can then run Jenkins with 1.7.0 and build using maven and the
older JDK
http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.htmlstrikes
again!
On 5 February 2014 14:20, marathiboy
Thanks Richard,
I understand that Java 1.6.0_71 is NOT freely available, however, since I am
just compiling (Jenkins's tomcat is running under Java 1.7), I thought this
should show me compilation error from my code and never expected to see
errors from Jenkins side.
Due to COTS issue, we must sti
Unfortunately I'm not sure how many people will be able to help you out
given that Patch 71 isn't generally publicly available.
Richard.
On Wed, Feb 5, 2014 at 3:40 PM, Ligade, Shailesh [USA] <
ligade_shail...@bah.com> wrote:
> Hello,
>
> We have to compile with java 1.6.0_71 and I am seeing t
Hello,
We have to compile with java 1.6.0_71 and I am seeing this build issue. Not
sure, if this is related to Jenkins, but since the error states that, I just
wanted to rule out that possibility.
Appreciate, if anyone can tell me, how to get this compiled under 71
(apparently 1.6.0_65 can co
