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

dependency-updates-report: limit to only artifacts that have updates and are in the dependency graph #589

Closed
jdavis4452 opened this issue May 12, 2022 · 1 comment · Fixed by #640

Comments

@jdavis4452
Copy link

jdavis4452 commented May 12, 2022

I am curious if it can be possible to limit this report to only show dependencies that have updates and only show dependencies that are in the dependency graph?

We have a dependency mgmt pom that is shared across our assemblies and currently the report shows all the imported dependencies. So it shows more than what is in the dependency graph for the assembly.

I tried setting <processDependencyManagementTransitive>false</processDependencyManagementTransitive>. That doesn't give me what I want though because it also gets rid of all the imported dependencies. Some of these are in the dependency graph and we want to see those in the report, we just want to exclude those that aren't in the dependency graph for the assembly. I think we need a setting to exclude dependencies that aren't in the dependency graph.

Also it would be nice if it would only show the dependencies that have updates
For example:
image
It would be nice if there was a setting to exclude dependencies that don't have updates.

@jarmoniuk
Copy link
Contributor

I'll gladly take it up.

jarmoniuk added a commit to jarmoniuk/versions-maven-plugin that referenced this issue Aug 19, 2022
Added `onlyUpgradable`, which will restrict the reports to only show upgradable artifacts, and `onlyProjectDependencies`, `onlyProjectPlugins`, which will restrict the graph of demendencyManagement/pluginManagement artifacts to the graph used in the project.

Additionally, some refactoring and improvements.
jarmoniuk added a commit to jarmoniuk/versions-maven-plugin that referenced this issue Aug 20, 2022
…raph (mojohaus#589)

Added `onlyUpgradable`, which will restrict the reports to only show upgradable artifacts, and `onlyProjectDependencies`, `onlyProjectPlugins`, which will restrict the graph of demendencyManagement/pluginManagement artifacts to the graph used in the project.

Additionally, some refactoring and improvements.
jarmoniuk added a commit to jarmoniuk/versions-maven-plugin that referenced this issue Aug 20, 2022
…raph (mojohaus#589)

Added `onlyUpgradable`, which will restrict the reports to only show upgradable artifacts, and `onlyProjectDependencies`, `onlyProjectPlugins`, which will restrict the graph of demendencyManagement/pluginManagement artifacts to the graph used in the project.

Additionally, some refactoring and improvements.
jarmoniuk added a commit to jarmoniuk/versions-maven-plugin that referenced this issue Aug 20, 2022
…raph (mojohaus#589)

Added `onlyUpgradable`, which will restrict the reports to only show upgradable artifacts, and `onlyProjectDependencies`, `onlyProjectPlugins`, which will restrict the graph of demendencyManagement/pluginManagement artifacts to the graph used in the project.

Additionally, some refactoring and improvements.
jarmoniuk added a commit to jarmoniuk/versions-maven-plugin that referenced this issue Aug 20, 2022
…raph (mojohaus#589)

Added `onlyUpgradable`, which will restrict the reports to only show upgradable artifacts, and `onlyProjectDependencies`, `onlyProjectPlugins`, which will restrict the graph of demendencyManagement/pluginManagement artifacts to the graph used in the project.

Additionally, some refactoring and improvements.
slawekjaranowski pushed a commit that referenced this issue Aug 20, 2022
…raph (#589)

Added `onlyUpgradable`, which will restrict the reports to only show upgradable artifacts, and `onlyProjectDependencies`, `onlyProjectPlugins`, which will restrict the graph of demendencyManagement/pluginManagement artifacts to the graph used in the project.

Additionally, some refactoring and improvements.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants