Just “supporting” Jakarta EE 10 Core profile and actually being compatible are two different things. TomEE 10 will of course support Jakarta EE 10 Core Profile - all your favorite specs are available; CDI 4.0, JAX-RS 3.1, JPA 3.1 and so on. You name it.
However actually being a fully compatible implementation is _a lot_ more work as this means we need to 100% pass the tremendously large set of tests for Jakarta EE 10 Core Profile. And I’m afraid we just don’t have the bandwidth available right now (as in contributing developers) to achieve this in any meaningful amount of time. What David meant is this will also mean that TomEE 10 will not be listed on start.microprofile.io <http://start.microprofile.io/> anytime soon. Richard also started a different discussion recently on what we want the roadmap to a final TomEE 10.0.0 release look like: https://lists.apache.org/thread/3bgzxl6ky2pzz95otovpmptmldyvoc3c Thanks Markus > On 22. Oct 2024, at 19:19, Memo Díaz Solis <diaz...@gmail.com> wrote: > > Just curious, will TomEE support Jakarta EE 10 Core profile? > > El lun, 21 oct 2024 a la(s) 11:16 a.m., David Blevins ( > dblev...@tomitribe.com) escribió: > >> Going to 7 would make the most sense. Note, though, we won't be able to >> claim Microprofile 7 compliance and be listed in on microprofile.io < >> http://start.microprofile.io/> as we're not Jakarta EE 10 Core profile >> certified. Unfortunately that's a requirement. >> >> >> -David >> >> >>> On Oct 21, 2024, at 12:27 AM, Markus Jung <ju...@apache.org> wrote: >>> >>> Hey all, >>> >>> >>> during regular dependabot upgrades I noticed we are already on MP Config >> 3.1 which is MP 6.1 while everything else is targeting MP 6.0 right now. >>> >>> Turns out, we have 3 Microprofile versions to choose from we can >> implement in TomEE 10 - 7.0, 6.1 and 6.0 as all of them share Jakarta EE 10 >> as a baseline requirement. TomEE is still not GA so we can still do bigger >> changes, this makes me seriously consider if we should just make the jump >> to 7.0 right now. >>> >>> >>> As far as I can tell we need to: >>> >>> - Upgrade to telemetry 2.0 (was stuck until recently because of OWB-1441) >>> - Remove MP Metrics >>> - Upgrade OpenAPI, Rest Client and Fault Tolerance to their newest >> implementations >>> >>> >>> WDYT? >>> >>> >>> Thanks >>> >>> Markus >>> >> >>
