Yes, ActiveMQ 7.x is a ways off. Having a Java module-friendly client-jar would
be interesting though. In the past, we’ve added transition jars to the tree
(ie. Activemq-cliekt-jakarta in 5.18.x) and we could do something similar.
If you go down the route of making a shaded jar, share your shad
It looks like the OSGi version would be compatible code wise, but it appears
that it has not been packaged with a module-info unfortunately.
I was attempting to avoid using a shaded jar so that there is less dependency
micromanagement, but I may have to look in to that route if we wish to proceed
Hi Christopher-
I cannot confirm that ActiveMQ is packaged to align with Java modules. The
broker does depend on classes in the client jar, so if you depend on the
broker, it will drag the client classes.
Since ActiveMQ has been prevalent for so long, moving packages to proper
separation will
Sorry I did it twice as I thought I entered in the wrong email!
From: Freeman, Christopher
Sent: Tuesday, October 15, 2024 4:54 PM
To: 'users@activemq.apache.org'
Subject: ActiveMQ Classic Broker and Client Module Issue
Hello all,
We are in the process of upgrading our application f
Hello all,
We are in the process of upgrading our application from Java 8 to 17 using
ActiveMQ Classic version 6.1.2. I am learning about the modules as I go so I
apologize if this much easier than it seems.
While setting up our module-info, in it we require the activemq.broker and
activemq.c
