[GRADLE-3423] Gradle fails to resolve inner classes in build.gradle Created: 30/Mar/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 2.12, 2.13
Fix Version/s: None

Type: Bug
Reporter: Sterling Greene Assignee: Cédric Champeau (Inactive)
Resolution: Won't Fix Votes: 0

Known Issue Of:



We are trying out gradle 2.12 with our existing build and it appears to have an issue which doesn't exist with the previous versions. I've been able to define a simple build.gradle file which reproduces the issue. This build file works perfectly fine with gradle 2.9 and 2.11 but with 2.12 the error message when processing the build.gradle is:

FAILURE: Build failed with an exception.

Build file '***********/build.gradle' line: 9

What went wrong:
Could not compile build file '******/build.gradle'.

startup failed:
build file '***********/build.gradle': 9: unable to resolve class Map.Entry
@ line 9, column 1.
for(Map.Entry entry : properties.entrySet()) {

Comment by Sterling Greene [ 29/Apr/16 ]

This has been fixed for the simpler case (Map.Entry) where the import or reference is for an inner class.

This still fails for references to inner-inner classes (inner classes of inner classes). The workaround for that case is to import the inner class and use qualified references to the inner-inner class.

So if you have

class Outer {
   class Inner {
      class MostInner {}

This will not work

import Outer.Inner.MostInner // fails here
MostInner foobar = null

This will work

import Outer.Inner
Inner.MostInner foobar = null
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:48:25 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.