Re: Changing default JDK for a job...

So it's now working with no changes that I can tell other than possibly restarting Jenkins. I went to install the Setenv plugin, found it was deprecated in favor of the "Environment Inject" plugin then noticed a new version of Jenkins (1.495) so I installed the Environment Inject plugin, downloa

Re: Changing default JDK for a job...

Looks like you need the Setenv plugin to get that option. On 12/28/2012 1:26 PM, Jeff wrote: I can't find anything in the "Build Environment" section that allows this. The check boxes I see are: Build Environment Delete workspace before build starts Copy files into the job's works

Re: Changing default JDK for a job...

I can't find anything in the "Build Environment" section that allows this. The check boxes I see are: Build Environment Delete workspace before build starts Copy files into the job's workspace before building [image: Help for feature: Copy files into the job's workspace before building]

Re: Changing default JDK for a job...

Your first question is a Maven issue - I could only speculate about it. For the second question - yes, in the Build Environment section of the job configuration you can set environment variables for the job. Eric On 12/28/2012 12:51 PM, Jeff wrote: Won't that will just cause clutter in the POM

Re: Changing default JDK for a job...

Won't that will just cause clutter in the POM that will affect every developer and every environment? Seems like it would be cleaner to just allow me to tell Jenkins to run the job using the correct JDK that was specifically defined in the job. My questions: - Why doesn't job execution honor

Re: Changing default JDK for a job...

You can do this using the Maven Compiler plugin. See http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html. Eric On 12/28/2012 12:25 PM, Jeff wrote: I have a brand new Jenkins master + slave running on top of the latest JDK 1.7.0_u10. I've configured