[GRADLE-3445] Cannot create a rule for specifying generatedBy for native source sets due to cyclic rule dependencies Created: 30/Apr/16 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Improvement | ||
Reporter: | Sterling Greene | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Description |
Based on the idl sample, you can specify a task that generates source code for a given LanguageSourceSet and the NativeComponentModelPlugin has rules to wire the generatedBy task into the dependencies for a binary. This requires the task to be defined before the source set in the model and the generatedBy to be set in the build script (because we need to provide a Task instance, not just a task name). Since we have a rule that mutates the Task container and takes the binaries (and eventually, source sets) to generate compile tasks, we can't have a different rule that mutates the source sets and takes the Task container. |
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:
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. |