Hi JB-
Unfortunately, I believe I need to -1 on this.
I believe the current best practice for bom is to have a fixed version, instead
of ${project.version}.
See Camel:
https://repo1.maven.org/maven2/org/apache/camel/camel-bom/4.7.0/camel-bom-4.7.0.pom
See Spring:
https://repo1.maven.org/maven2/org/springframework/spring-framework-bom/6.1.11/spring-framework-bom-6.1.11.pom
-Matt Pavlovich
> On Aug 2, 2024, at 1:50 AM, Jean-Baptiste Onofré <[email protected]> wrote:
>
> Hi everyone,
>
> I submit Apache ActiveMQ Classic 6.1.3 release to your vote.
>
> This release includes 16 fixes and updates, especially:
> - add a BoM
> - fixes on the Message REST API, especially concurrent access
> - Spring 6.1.11 update
> - fix NoClassDefFound on bin/activemq export command line
> - several dependency updates
>
> You can take a look on Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12354559
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1400/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/6.1.3/
>
> Git tag: activemq-6.1.3
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] 0 I don't care
> [ ] -1 Don't approve the release (please provide specific comment)
>
> This vote will be open for at least 72 hours.
>
> Thanks!
> Regards
> JB
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> For further information, visit: https://activemq.apache.org/contact
>
>
