[GRADLE-3060] Cannot resolve artifacts from an ivy repository using ivy extra attributes Created: 02/Apr/14 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Daz DeBoer | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Issue Links: |
|
||||||||
| Description |
|
The ivy.xml file supports the concept of custom extra attributes on an artifact element. In Ivy, these attributes can be included in the pattern used to locate the artifact. Currently it's not possible to use patterns that include Ivy extra attributes in Gradle. |
| Comments |
| Comment by Daz DeBoer [ 02/Apr/14 ] |
|
This issue addresses a specific deficiency in Gradle, and I believe covers the true original intent of 940. |
| 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. |