+1 I checked things out as follows: - Verified the signature and checksum files. - Checked for LICENCE and NOTICE files in the archives. - Used "mvn apache-rat:check" to check headers in the source archive. - Ran the build from the source archive on JDK25 - Connected the standalone console to a 2.50.0 broker instance and and had a poke around the console. - Integrated with the 2.51.0-SNAPSHOT broker build on JDK25 using https://github.com/apache/artemis/pull/6206 along with the staging repo and had a poke around the console. - Used a simple test pom to check over the relocation poms staged at https://repository.apache.org/content/repositories/orgapacheactivemq-1449 and verify dependencies on the console war and assembly zip using old GAVs got redirected to the new GAVs artifacts.
Robbie On Wed, 28 Jan 2026 at 11:12, Andy Taylor <[email protected]> wrote: > > I would like to propose an Artemis Console 1.5.0 release. The main > focus of this release is for dependency upgrades, mainly Jolokia > > The Binary artifacts can be found at > https://dist.apache.org/repos/dist/dev/artemis/artemis-console/1.6.0 > > The Maven staging repository is here: > https://repository.apache.org/content/repositories/orgapacheartemis-1009 > > If you would like to validate the release you can either: > > 1. Check out the source, build and follow the readme instructions > (README.md) to deploy and smoke test the console. > 2. Download the binary distribution and deploy in a web container. > 3. Replace the console war in the latest An Artemis release or a > build from source. > > [ ] +1 approve this release [ ] +0 no opinion [ ] -1 disapprove (and reason > why) > > Here's my +1 > > Andy Taylor --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
