[MNG-6757] Cant create a proper BOM when using ${revision}

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.6.1
• Fix Version/s: 4.0.x-candidate, waiting-for-feedback
• Component/s: Core, Errors
• Environment: Ubuntu 18.04
• Assignee: Unassigned
• Reporter: Kalle Widell
• Created: 04/Sep/19 08:04
• Updated: 19/Jul/22 21:06

Description

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

 

Issue Links

• is fixed by: MNG-6656 Introduce base for build/consumer process