[
https://issues.apache.org/jira/browse/MPH-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPH-183:
------------------------------
Description:
The popular spring-boot makes a lot of use of BOMs. Using BOMs is a good
practice, but right now it is very hard to determine where dependencyManagement
dependencies and especially their versions are coming from.
Instead of only showing only the final location (from the BOM POM), it should
also show the import path from the current project to that specific pom (where
is the BOM POM imported?).
This way it will be easier to figure out which dependency in which POM needs to
be upgraded: it's the version in the POM declaring the import of the BOM POM,
not the version in the imported BOM POM.
was:
The popular spring-boot makes a lot of use of BOMs. Using BOMs is a good
practice, but right now it is very hard to determine where dependencies and
especially their versions are coming from.
Instead of only showing only the final location (from the BOM POM), it should
also show the import path from the current project to that specific pom (where
is the BOM POM imported?).
This way it will be easier to figure out which dependency in which POM needs to
be upgraded: it's the version in the POM declaring the import of the BOM POM,
not the version in the imported BOM POM.
> Effective-pom + verbose should show import path to BOM dependencyManagement
> ---------------------------------------------------------------------------
>
> Key: MPH-183
> URL: https://issues.apache.org/jira/browse/MPH-183
> Project: Maven Help Plugin
> Issue Type: Improvement
> Affects Versions: 3.2.0
> Reporter: Robert Scholte
> Assignee: Maarten Mulders
> Priority: Major
> Attachments: mph-183-it.zip
>
>
> The popular spring-boot makes a lot of use of BOMs. Using BOMs is a good
> practice, but right now it is very hard to determine where
> dependencyManagement dependencies and especially their versions are coming
> from.
> Instead of only showing only the final location (from the BOM POM), it should
> also show the import path from the current project to that specific pom
> (where is the BOM POM imported?).
> This way it will be easier to figure out which dependency in which POM needs
> to be upgraded: it's the version in the POM declaring the import of the BOM
> POM, not the version in the imported BOM POM.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
