[GRADLE-1694] 'gradle dependencies' should include more information Created: 26/Jul/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 1


Initially reported at zendesk: http://support.gradleware.com/tickets/1024

It would be good if gradle dependencies included additional information (in ivy terms):

  • origin-location
  • rev-constraint-dynamic

Examples of ivy xmls that include above information:

<metadata-artifact status="successful" details="" size="853" time="48" location="xxx" searched="true" original-local-location="xxx" origin-is-local="false" origin-location="http://myserver.com/xxx/ivy.xml"/>

<caller organisation="tripwire.com" name="teagent" conf="rtmppk" rev="1.0.0" rev-constraint-default="1.0.0" rev-constraint-dynamic="1.0+" callerrev="8.1.0"/>

Comment by Adam Murdoch [ 06/Dec/12 ]

Can we close this now?

Comment by Szczepan Faber [ 10/Dec/12 ]

I'm not sure because the user also wanted the origin-location. I assume that 'rev-constraint-dynamic' is what we already show in the dependency reports (requested->selected) since Gradle 1.2.

Watchers/voters, can we close this ticket now?

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:01:59 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.