[GRADLE-1989] Provide API to construct a dependency repository of project's dependencies Created: 09/Dec/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: | Luke Daley | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 1 |
Description |
The Grails project distributes its dependencies as part of its distribution. Its runtime uses Ivy to resolve dependencies, so it needs to distribute the dependencies as an Ivy repository. This means it needs the ivy.xml descriptors. The only way to achieve this right now is to pull out the descriptors from the cache, which is problematic as the cache is designed to be opaque and may change from version to version. See: https://github.com/grails/grails-core/blob/master/gradle/assemble.gradle#L46 |
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. |