Hi JB, thanks for the info. Guess we will come back to your offer once there is a decission regarding the java baseline.
Just started a discussion if we can move "main" (TomEE 10) to a Java 17 baseline in order to integrate AMQ6 + CXF 4.1 in the near future. Gruß Richard Am Donnerstag, dem 04.04.2024 um 16:46 +0200 schrieb Jean-Baptiste Onofré: > Hi Richard, > > Just a minor note about ActiveMQ 6.x: the JMS3 support is not yet > full, meaning that some specific operations can throw > OperationNotSupportedException. > > ActiveMQ 6.1.1 is currently on vote (I will release it tomorrow), > including a couple of new JMS3 operations. > I estimate that JMS3 full support should come around ActiveMQ 6.3. > > Please let me know if I can help in any way :) > > Regards > JB > > On Sun, Mar 31, 2024 at 11:30 AM Richard Zowalla <r...@apache.org> > wrote: > > > > Hi all, > > > > just looked into AMQ (classic) 6.1.0 (JMS 3.1), which seems to be > > fully > > Jakarta compatible (currently running a CI build on a related > > branch). > > However, it requires Java 17 as a baseline (meh). > > > > Since EE10 targets Java 11+ (and not 17+), the question would be, > > if we > > can/want to upgrade? From a spec perspective, I assume, that we > > cannot. > > > > Why AMQ6: It would enable us to drop some of our shaded > > dependencies > > (and would be a thing for EE11 anyway). > > > > I am not familiar with the TCK requirements or if it is possible to > > only support one JVM runtime for certification? At a first glance > > at > > [1], there are vendors (fujitsu), who only did the TCK runs on Java > > 17, > > but I am not familiar with the actual details of the process. > > > > Happy to get some thoughts on it. > > > > (Not planning to have such a change in the proposed milestone, just > > want to get some thoughts on it) > > > > Gruß > > Richard > > > > > > [1] https://jakarta.ee/compatibility/certification/10/