[GRADLE-1476] Make AbstractCompile able to find the "root" of SourceSets Created: 15/Apr/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Robert Fischer Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

It'd be really nice if an inheritor of AbstractCompile could find the root directories of the source sets when compiling.

So if the source contains something like this:

./src/foo/sourcetype/com/something/dooit.sourcetype

It'd be nice to get a handle on:

./src/foo/sourcetype

The reason this is relevant is because some compilers (e.g. Mirah) are sensitive to the directory structure in order to infer packages.

I have no idea what the best way is to get that information into the compiler, which is why I'm opening this as a Minor Wish instead of submitting a patch. But I want to get it on the radar of the Gradle developers that it'd be nice to pander to directory structure sensitivity for certain compilers.

 Comments   
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 11:56:29 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.