Hi Jean-Baptiste, Thanks for your reply. IT was helpful!
> 1. Yes, you can us activemq-client-jakarta with connection factory > pooling, nothing change here. > Using org.apache.activemq:activemq-jms-pool:5.18.2 if am not wrong? Can you please point me to an example or a test case? > 2. Yes, 5.19.0 will never happen, instead we will release 6.0.0. I'm > working on updating the website about that. > 3. Basically the roadmap is on Jira for now. As I said on point 2, I'm > updating website (complete refactoring of the AMQ component area) > 4. For Spring Boot and Camel, you can use 5.18.x, it should work without > problem > 5. Soon, as part of the website update > > Regards > JB > > On Thu, Oct 12, 2023 at 5:45 PM Daoud Abdelmonem Faleh > <abdelmonem.fa...@gmail.com> wrote: > > > > Hello ActiveMQ folks, > > > > We are in the process of migrating to Spring-boot 3.1 and Apache Camel > 4.0. > > from Spring-boot 2.7 and Camel 3.14 > > Our components make use of PooledConnectionFactory from artifact > > org.apache.activemq:activemq-jms-pool . Version 5.18.2 of the mentioned > > artifact depends on javax.* namespace. > > > > In order to align with jakarta.* namespace being used in target version > of > > Spring and Camel, we thought we could go with the 5.19-SNAPSHOT+ version > in > > the hope it gets released in time for our internal release. However I see > > that 5.19-SNAPSHOT hasn't been updated since Sep 09 while the most > current > > update on the snapshot repository from Oct 10 and main branch points to > > 6.0.0-SNAPSHOT. > > > > So, my questions are: > > - is there any known way to use the latest release of > > activemq-client-jakarta (5.18.2) with connection pooling? > > - is 5.19.0 being skipped in favor of 6.0.0 ? > > - if there is some formel/informel release roadmap that I couldn't > find > > ? > > - should I go with 6.0.0-SNAPSHOT ? > > - and if someone could point me to some documentation about the > > breaking changes from 5.X to 6.X. ? > > > > > > Thanks for your time, > > --Daoud. >
