[GRADLE-3173] Gradle 1.12: sourceCompatibility not handled correctly in IDEA project generation for multi-project builds Created: 25/Sep/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


I have a multi-project build with 2 projects, each with a different sourceCompatibility setting (one is 1.8, the other is 1.6). When I generate an IDEA project from this build, it does not set up the correct IDEA settings. In particular what happens is:

1. A Project SDK of 1.6 is selected
2. A Project language level of 6.0 is selected.
3. Each module is set with a language level of "use project language level".

I would instead expect:

1. A Project SDK of 1.8 to be selected (since that is the higher of the two). This allows the 1.8 code to compile and of course a 1.8 JDK can also compile 1.6 code.
2. A Project language level of 8.0 is selected. I expect this because my "root" project is the 1.8 project.
3. The language level of the 1.8 project should be set to either 8.0 or "use project language level". I don't have strong feeling about this. The language level of the 1.6 project should be set to 6.0.

Comment by Gradle Forums [ 25/Sep/14 ]

I haven't had a chance to look at this yet but it sounds like something what should be fixed. Do you know if IntelliJ import of Gradle projects handles this correctly? They may do some extra step to tune the setup of imported project/modules.

It would be great to have a contribution for this improvement as this would make it faster to see a release where this is fixed.

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