Hi Art, I disagree: as said on Slack, it works fine with JMS 1.1 with you provide the right bundle (thanks to dependency flag). So, it's possible to still use JMS 1.1 bundle (geronimo) if you provide before installing the activemq-client feature. If you don't provide jms 1.1 bundle, by default, the feature will install JMS 2.0.
As you described your use case in the Jira, I will reply directly there. Why not simply adding jms 1.1 in addition of 2.0 in the feature: that way, you can support both. I don't see why reverting this as it works fine (I'm using both JMS 1.1 and 2.0 in Karaf without problem). Anyway, I will reply in Jira. Regards JB On Mon, Jun 20, 2022 at 7:45 PM Arthur Naseef <a...@amlinv.com> wrote: > > I created the following ticket to address applications failing to load into > Karaf with AMQ 5.16.3 - 5.17.1 due to an incompatible change in the > activemq-client feature. > > https://issues.apache.org/jira/browse/AMQ-8971 > > > Looks to me like the right fix here is to revert the change to the JMS 1.1 > spec in the feature because all of the AMQ internals are still 100% on the > JMS 1.1 spec. The maven-bundle-plugin for client applications is doing the > right thing by generating "Package-Import" lines with version range > "1.1,2.0)", but the feature doesn't match it. > > It seems we have sacrificed the core case to solve an edge case. > > Thoughts? > > Art
