You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/12/25 16:32:00 UTC
[jira] [Comment Edited] (MNG-6757) Cant create a proper BOM when
using ${revision}
[ https://issues.apache.org/jira/browse/MNG-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254872#comment-17254872 ]
Michael Osipov edited comment on MNG-6757 at 12/25/20, 4:31 PM:
----------------------------------------------------------------
[~michael-o] Ok. I'll see to that such is provided.
was (Author: widell):
[~michael-o] Ok. ill see to that such is provided.
> 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
>
>
> 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)