Any plans to offer a Jakarta version?
See original GitHub issueIn playing around with migrating Hibernate to Jakarta Persistence APIs I ran into trouble with our hibernate-jcache
module. The only hang up I saw was that ehcache3 uses JAXB which would need to be updated to use Jakarta’s JAXB apis/impls.
Having done this for Hibernate I can offer some help/guidance. Let me know
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:22 (9 by maintainers)
Top Results From Across the Web
Our (bumpy) road to Jakarta EE 10 - Quarkus
EE 9 is back in town Well, actually, no. We won't publish any Jakarta EE 9-based version of Quarkus but… Jakarta EE...
Read more >Ambitious Plans to Build Indonesia a Brand New Capital City ...
Indonesia wants to build a $34 billion new capital city from scratch to help it reach high-income status by 2045. Source: Indonesia Ministry...
Read more >Jakarta EE 10 Release Plan - GitHub Pages
The Jakarta EE 10 Platform release plan covers the Platform and Web Profile specifications. As stated earlier, all component Specifications which plan a...
Read more >Jakarta EE 9 Release Plan Approved - Payara Blog
The approval of the Jakarta EE 9 Release Plan is a great milestone for the Jakarta EE project and a stepping stone towards...
Read more >A Java 17 and Jakarta EE 9 baseline for Spring Framework 6
This forward-looking baseline will provide significant benefits in our API ... If Jakarta EE 9 is the minimum version supported for Spring ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just one thing to check. The ‘default’ artifacts still use
javax
packages. The Jakarta version are variants, to depend on them in Maven you would need:or in Gradle (where everything will work more transparently)
Note: I typed the above from memory… I probably put in a bunch of typos and/or mistakes.
Very nice, thanks @chrisdennis!