[ https://issues.apache.org/jira/browse/MNG-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270780#comment-17270780 ]
Kalle Widell edited comment on MNG-6757 at 1/24/21, 6:16 PM: ------------------------------------------------------------- Sorry, been busy here. I did try tonight. Using apache-maven-4.0.0-alpha-1-20210115.141200-33-bin (taken from your CI server?!) i tried to build attached sample project. # mvn clean install # The installled/resulting .m2/....<intall-path>..../example-library-bom/pom.xml ("bom") does not replace usage of ${revision} in the dependencyManagegment->dependencis-> dependency : example-library-api clause of this file. Cant really remember the details here. But if another project depends om something containing ${revision} it gets confused? Can't remember the issue with project.version (from a users perspective they sound the same). These are not resolved either in the resulting bom. What did you hope should happen / changed? was (Author: widell): Sorry, been busy here. I did try tonight. Using apache-maven-4.0.0-alpha-1-20210115.141200-33-bin (taken from your CI server?!) i tried to build attached sample project. # mvn clean install # The installled/resulting .m2/....<intall-path>..../example-library-bom/pom.xml ("bom") does not replace usage of ${revision} in the dependencyManagegment->dependencis-> dependency : example-library-api clause of this file. Cant really remember the details here. But if another project depends om something containing ${revision} it gets confused? Can remember the issue with project.version (from a users perspective they sound the same). These are not resolved either in the resulting bom. What did you hope should happen? > Cant create a proper BOM when using ${revision} > ----------------------------------------------- > > Key: MNG-6757 > URL: https://issues.apache.org/jira/browse/MNG-6757 > Project: Maven > Issue Type: Bug > Components: core, Errors > Affects Versions: 3.6.1 > Environment: Ubuntu 18.04 > Reporter: Kalle Widell > Priority: Major > Fix For: 4.0.x-candidate, waiting-for-feedback > > Attachments: sample-project.tar.bz2 > > > When I have a multimodule project where one of the modules is a BOM, meant > for other projects. (Think spring boot starter bom) I see no way of using > ${revision} to make the resulting BOM have the version of the project to be > resolved in that bom. I cannot use ${project.version} in the BOM for this, as > these wont be resolved upon install/deploy. > Apart from the BOM part Ive set up my project according to > [https://maven.apache.org/maven-ci-friendly.html] > Also made a ticket here > [https://github.com/mojohaus/flatten-maven-plugin/issues/104] > -- This message was sent by Atlassian Jira (v8.3.4#803005)