[GRADLE-3343] Groovy Compiler always uses the same version of Java as the Gradle build Created: 30/Sep/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Sterling Greene Assignee: Unassigned
Resolution: Won't Fix Votes: 2

Attachments: Zip Archive ticket-1509.zip    



  • Run Gradle with JDK7
  • Set compatibility flags for JDK8
  • Compile Java code for JDK8 (by explicitly configuring JavaCompile/GroovyCompile)
  • Compile Groovy code that uses the Java classes

This results in a java.lang.UnsupportedClassVersionError because the Groovy compiler is running with JDK7 but sees class files from Java compilation (compiled with JDK8). There's no way to specify a different Java path to be used by the Groovy compiler.

An example:


Attached is an example project that exhibits the problem when run with JDK7.

Comment by Eric Deandrea [ 30/Sep/15 ]

We need a way to get the Groovy compiler to fork correctly when a different jdk is specified other than the jdk that is running gradle itself.

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:46:19 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.