[GRADLE-2689] Gradle fails extending configuration from parent project Created: 22/Feb/13 Updated: 22/Nov/16 Resolved: 22/Nov/16
|Affects Version/s:||1.0-milestone-6, 1.0-milestone-9, 1.0, 1.4|
We declare some configurations in the root project, which are used to extend configurations in child projects.
Unfortunately it causes a NPE:
On 1.0-milestone-3 the result is:
The two (simple!) example projects are included in gradle-npe.zip.
This works on 1.0-milestone-3. The versions I've tested are listed in Affected Versions.
|Comment by Jesper Skov [ 11/Mar/13 ]|
Same behavior on 1.5-rc-1
|Comment by Jesper Skov [ 24/Jun/13 ]|
I just tried poking around in the code to see if I could fix it.
Not sure I succeeded, because I have not understood enough of the code to be sure.
But the below patch makes the little test attached above work.
I don't understand how the hierarchy entries translate to artifacts; the method in the same class asks Ivy.
|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 Jesper Skov [ 16/Nov/16 ]|
Please close it.
|Comment by Benjamin Muschko [ 22/Nov/16 ]|
Closing as indicated by comment.