You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
report for
Possible Solutions:
The text was updated successfully, but these errors were encountered: