gnodet commented on issue #8503:
URL: https://github.com/apache/maven/issues/8503#issuecomment-4110310132
This issue is fixed in Maven 4 through the **consumer POM** feature.
Maven 4 introduced consumer POM generation (`DefaultConsumerPomBuilder`)
which automatically resolves CI-friendly version properties like `${revision}`,
`${sha1}`, and `${changelist}` when producing the POM that gets
installed/deployed. This means:
1. The BOM you author locally can use `${revision}` freely
2. When installed/deployed, the consumer POM contains the resolved version
values
3. Other projects importing the BOM via `<scope>import</scope>` see proper
resolved versions
Key commits:
- `885a4b3a26` — [MNG-8230] Rewrite CI-friendly versions
- `82adfd9bd4` — Fix BOM packaging in consumer POMs
- Multiple subsequent fixes for BOM packaging in consumer POMs
(`ba5c9a4ff1`, `3465bf14c2`)
This is now core Maven 4 functionality and works out of the box.
_Claude Code on behalf of Guillaume Nodet_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
