We aim for EE10 in TomEE 10. The core spec in [1] lists the required Specs, which are all in TomEE 10. However, passing the TCK and actually be compliant versus just support it, is a different story.
[1] https://jakarta.ee/specifications/coreprofile/10/jakarta-coreprofile-spec-10.0#core-profile-definition Am 22. Oktober 2024 19:19:09 MESZ schrieb "Memo Díaz Solis" <diaz...@gmail.com>: >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 >> > >> >>
