[GRADLE-774]  Create a project report that discovers if newer versions of a dependency are available. Created: 09/Dec/09  Updated: 03/Feb/17  Resolved: 03/Feb/17

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

Type: Improvement
Reporter: Philip Crotwell Assignee: Unassigned
Resolution: Duplicate Votes: 5


 Description   

Is it possible with ivy to see if there is a more recent version of a
dependency available? If so, that would make a great addition to the
project reports plugin. I know from my own projects it is a real pain
to go through each dependency, find the web site, find the current
version and compare against my dependency list. If this were possible,
it would help keep everybody current.

 Comments   
Comment by Hans Dockter [ 12/Dec/09 ]

This is a nice idea.

Comment by Sean Griffin [ 22/Mar/12 ]

FWIW this is similar to the functionality provided in Maven by the versions-maven-plugin:display-dependency-updates and dependency-updates-report. One feature that would make this much better than Maven's version, however, would be having it show the available later versions not just for the declared dependencies but also for the transitive dependencies.

My most common use case for this is when building assemblies (WARs, EARs, etc.) and wanting to see what bug fix versions might be out there that I should consider upgrading to.

Comment by Ben Manes [ 06/Dec/12 ]

A basic report is now available in the versions plugin (https://github.com/ben-manes/gradle-versions-plugin). It would be nice to see this capability provided directly as a project report.

I think transitives should be easy to add (currently transitives are not resolved to be faster). You can request a feature or provide a pull request.

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 Ben Manes [ 15/Nov/16 ]

I would prefer that this functionality was provided directly by Gradle. The plugin is popular enough that it is even shown on the Gradle website next to the built-in reports.

Comment by Mathias Kalb [ 03/Dec/16 ]

Comment by Benjamin Muschko [ 03/Feb/17 ]

The work is now tracked on GitHub: https://github.com/gradle/gradle/issues/1318

Generated at Wed Jun 30 11:38:33 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.