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

[jira-importer]

Kalle Widell opened MNG-6757 and commented

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 mojohaus/flatten-maven-plugin#104

 

---

Affects: 3.6.1

Attachments:

• sample-project.tar.bz2 (1.33 kB)

Issue Links:

• MNG-6656 Introduce base for build/consumer process
  ("is fixed by")

Backported to: waiting-for-feedback

[jira-importer]

Michael Osipov commented

Can you retry with Maven from master?

[jira-importer]

Kalle Widell commented

Michael Osipov Im on vacation until jan 4:th. Would it be okey to test it then or do you really need feedback earlier? I much appreciate this fix as it would make life so much easier for us. So can rush it if time is scarce.

[jira-importer]

Michael Osipov commented

No issue, take your time. Providing a sample project would have been way easiser for us to verify a possible fix.

[jira-importer]

Kalle Widell commented

Michael Osipov Ok. I'll see to that such is provided.

[jira-importer]

Michael Osipov commented

Did you test?

[jira-importer]

Kalle Widell commented

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.

1. mvn clean install
2. 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? 

 

 

[jira-importer]

Kalle Widell commented

Michael Osipov Do you have what is needed? Do I need to clarify anything?

 

[jira-importer]

Michael Osipov commented

Can you check whether your issue could be related to any of these:

• https://issues.apache.org/jira/browse/MNG-6727
• https://issues.apache.org/jira/browse/MNG-2971
• https://issues.apache.org/jira/browse/MNG-6578
• https://issues.apache.org/jira/browse/MNG-6746
• https://issues.apache.org/jira/browse/MNG-6253
• https://issues.apache.org/jira/browse/MNG-6438
• https://issues.apache.org/jira/browse/MNG-6507

[jira-importer]

Michael Osipov commented

Still waiting for an answer...