[GRADLE-2590] Gradle tries to downloads artifactory metadata despite using artifact only notation Created: 06/Dec/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Daniel Beck Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

Dependencies specified using the map syntax with "ext" key should ignore any repository metadata (ivy.xml, Maven pom).

As per User Guide '44.4.1.2 Artifact only notation' and 'Example 44.5. Artifact only notation' one would assume that Gradle doesn't try to access the metadata.

For a metadata-free repository of zip files, trying to access the metadata is a waste of time.

This is an issue of either documentation (why is the metadata is still required?) or dependency management (don't attempt to download metadata that gets ignored anyway).

 Comments   
Comment by Keir Lawson [ 22/Apr/15 ]

This is still an issue with Gradle 2.2

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 12:26:04 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.