Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature-Request] mvn version:display-dependency-updates --limit <dependency> to check only a specific dependency #212

Closed
tillmannheigel opened this issue Sep 25, 2017 · 10 comments

Comments

@tillmannheigel
Copy link

tillmannheigel commented Sep 25, 2017

It would be great to have an option thats limits version checks for a single dependency (or a group, or a group pattern).

Especially for large projects or slow repositories it's annoying to check all dependency everytime.

I will open a PR as soon as possible.

@rsrini7
Copy link

rsrini7 commented May 15, 2020

2.5 Years + Old issue. Any resolution ?
Each commit, jenkins takes more than 20 mins to check all irrelevant repos (entire mvn dependency chain. )

@tillmannheigel
Copy link
Author

Thx for the reminder.

@naiyerasif
Copy link

This is the single most important reason why I'm not using this plugin in my projects. It takes way too long to finish, especially in case of large dependency graphs and multiple Maven profiles.

I'd suggest a way to configure the depth of dependency scan that this plugin should do (e.g., a depth = 0 should only show me the updates applicable for the dependencies explicitly mentioned in the POM of the current project). In case of a BOM, I'd like to restrict the scan to limit to what versions the BOM dictates.

@somejavadev
Copy link

@tillmannheigel @rsrini7 @naiyerasif

I also require this functionality. I have made a pull request so long but you are more than happy to try it out. The new parameter is called includes (similar to the dependency tree plugin)

mvn versions:display-dependency-updates -Dincludes=org.springframework.boot:spring-boot-starter-data-jpa,org.hibernate

@tillmannheigel
Copy link
Author

Thx a lot, I kind of lost track :)

@somejavadev
Copy link

@tillmannheigel Not a problem at all. It is the first time I am contributing to this project so there might be some changes required to my PR. I am however using the PR version without any problems.

@drycode
Copy link

drycode commented Jan 27, 2022

@somejavadev Any updates on this issue? I'd be happy to chip in to get this over the finish line if I can

@jarmoniuk
Copy link
Contributor

jarmoniuk commented Sep 4, 2022

Looks like this has already been merged into the upcoming 2.12.0 release!

@jarmoniuk
Copy link
Contributor

jarmoniuk commented Sep 4, 2022

Duplicate of #318 @slachiewicz

@somejavadev
Copy link

@drypycode apologies for the late reply but I see @ajarmoniuk already replied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants