Yes. Let's use the major release to remove the components not ready. As Romain says it's easy to add them back if needed
Le mar. 25 avr. 2023, 09:13, Romain Manni-Bucau <[email protected]> a écrit : > Agree, I also think we can drop all our extensions "components" since the > reusability was never reached (it is always faster and simpler to implement > your component) so let's keep only jbatch and UI/tools related modules > maybe? > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github > <https://github.com/rmannibucau> | LinkedIn > <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > Le mar. 25 avr. 2023 à 08:52, Richard Zowalla <[email protected]> a > écrit : > >> Hi, >> >> aside from the upgrade killing our active waiting strategy in the tests >> for the DirectEndpoint, I am seeing >> >> Caused by: java.lang.ClassNotFoundException: >> javax.activation.DataHandler >> at >> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClass >> Loader.java:641) >> at >> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Cla >> ssLoaders.java:188) >> at >> java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520) >> ... 82 more >> >> with the 2.25.x version of camel during the tests (if I workaround the >> protected getConsumer() via a wrapper strategy, see [1]). However, the >> tests will pass... >> >> This gives me the impression, that Camel 2.x isn't jakarta ready. From >> looking into their Jira it seems, that Camel 4.x will be jakarta ready >> (Java 17 as baseline) but for now upgrading would make it rather >> useless (or we would need to relocate). >> >> Gruß >> Richard >> >> [1] >> >> https://github.com/rzo1/geronimo-batchee/commit/6cc27362b7a0bb34a8bd3d39a1fe35c4a5f834b3 >> >> >> >> Am Freitag, dem 21.04.2023 um 13:13 +0200 schrieb Mark Struberg via >> dev: >> > Hi folks! >> > >> > I've now finished the work on BatchEE-2.0.0. >> > I think we have to enable the TCK still, but all our internal tests >> > do work again. >> > >> > Note that I had to move back to an old Camel version due to getting >> > test errors with a newer version. >> > Would be great if someone could please take a look at it! >> > >> > LieGrue, >> > strub >> >>
