You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2023/03/13 06:50:00 UTC

[jira] [Commented] (MPH-183) Effective-pom + verbose should show path to BOM import

    [ https://issues.apache.org/jira/browse/MPH-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699479#comment-17699479 ] 

Herve Boutemy commented on MPH-183:
-----------------------------------

nice, we now see in which parent POM the BOM POM was imported
question:
- instead of generic "from", should not we be more specific "from BOM imported in"?
- I see there is no line number: we should probably find a way to point to a line number

> Effective-pom + verbose should show path to BOM import
> ------------------------------------------------------
>
>                 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 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 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)