You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Falko Modler (Jira)" <ji...@apache.org> on 2022/02/13 22:38:00 UTC

[jira] [Commented] (MNG-6378) Properties from POM in import scope should be resolvable in the project

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

Falko Modler commented on MNG-6378:
-----------------------------------

This would be useful in Quarkus:
- BOM defines e.g. {{kotlin.version}} https://github.com/quarkusio/quarkus/blob/main/bom/application/pom.xml#L147
- Some modules like the following need the {{kotlin-maven-plugin}}, e.g.: https://github.com/quarkusio/quarkus/blob/main/extensions/resteasy-reactive/quarkus-resteasy-reactive-kotlin-serialization/runtime/pom.xml#L41
- So {{build-parent}} has to duplicate the {{kotlin.version}} property: https://github.com/quarkusio/quarkus/blob/main/build-parent/pom.xml#L23 (to use it here: https://github.com/quarkusio/quarkus/blob/main/build-parent/pom.xml#L765)

This can easily diverge, causing maintenance issues. Dependabot doesn't catch it either.

> Properties from POM in import scope should be resolvable in the project
> -----------------------------------------------------------------------
>
>                 Key: MNG-6378
>                 URL: https://issues.apache.org/jira/browse/MNG-6378
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Jakub Kubrynski
>            Priority: Major
>             Fix For: waiting-for-feedback, wontfix-candidate
>
>
> Properties defined in the POM that is in the import scope in the dependencyManagement section should be able to resolve in the project. It's especially important in the framework (like Spring) using BOM patterns



--
This message was sent by Atlassian Jira
(v8.20.1#820001)