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

Enhancement: limit report to updates actionable in the context of pom.xml #1140

Open
rmie opened this issue Sep 18, 2024 · 0 comments
Open

Comments

@rmie
Copy link

rmie commented Sep 18, 2024

I found nothing similar in closed issues, if you consider this a duplicate to a previous issue, feel free to close it.

Motivation:
I'm trying to limit the reports down to a point that all listed dependencies, plugins, parent and properties version are specified in the analyzed pom.xml. Basically all inherited (upstream) issues should be ignored. I want to make it as simple and fast as possible to fix such issues without the need to reason about if a reported issue is inherited from upstream.

Example: two projects, from different reactors

  • parent/pom.xml uses spring-boot-starter-parent:3.3.1, but 3.3.3 is latest version
  • service/pom.xml uses parent/pom.xml at latest version

report for

  • parent/pom.xml
    • MUST list outdated parent
    • MUST NOT list e.g. outdated plugins, dependencies that are inherited from spring-boot-starter-parent
  • service/pom.xml
    • MUST NOT list e.g. outdated parent, plugins etc. inherited from parent/pom.xml

Possible Solutions:

  • preferred, additional flag e.g. ignoreInherited to control this behavior
  • alternative, mark "inherited" issues in reports (and possibly xml) as such
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

1 participant