[GRADLE-2453] sourceCompatibility ignored when running with the org.gradle.java.home option Created: 29/Aug/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.1
Fix Version/s: None

Type: Bug
Reporter: Mike M. Assignee: Unassigned
Resolution: Won't Fix Votes: 0


I have a build that needs to run with jdk6. However, the software being built needs to be run on jdk5. Specifying

sourceCompatibility = 1.5

achieves this (the compiler generates java1.5-compatible class files).

Now I'm running our build on a system where JAVA_HOME and the PATH were set to a jdk1.5. Since I (initially) didn't want to alter the build environment there, I simply added


in the gradle launch.

When doing so, everything seems to work as expected, but all generated class files are java1.6 class files, so it looks like the sourceCompatibility gets ignored in this scenario.

I then created a simple test project to reproduce the problem and added

println "Running on Java: ${System.getProperty('java.version')}"

at the top of the buildfile. Surprisingly, even with the org.gradle.java.home option set to the 1.6 jdk, it still said it was running on the java5 vm.

I had expected gradle to fork a completely new VM before even starting the build, but that's apparently not the case. This behavior might be surprising and even disturbing (imagine if someone does jdk-specific things in the build and gets the wrong jdk version number...)!

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:22:20 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.