-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jakarta support #447
Comments
It is on TODO list, but I have no time for it now. I'm still using java EE 8. |
Hi @skybber, can you please tell me what is the status of Jakarta support? Pull request #449 is closed (by @amoscatelli) but not merged, AFAICT. |
There are many new *_jakarta plugins: https://github.com/HotswapProjects/HotswapAgent/tree/master/plugin it should work except weld_jakarta, that is not tested at all. owb_jakarta should work. |
I've just tried the version 1.4.2-SNAPSHOT (2023-07-14) with project using Jakarta versions of Hibernate (6.2.7), Weld (5.0.SP3) and Jakarta Faces / Mojarra (4.0.3) on JDK17 (JetBrains Runtime JDK jbr_jcef-17.0.8-windows-x64-b1000.8) and Tomcat 10.1.13 (configured according to JDK17 quick start guide). Mojarra plugin fails with following:
It seems that there is no "jakarta" version of mojarra plugin? |
Problem here is not that plugin is not "jakartified" but that Mojara plugin in version 1.4.2-SNAPSHOT does not work with Jakarta Faces / Mojarra (4.0.3). In new 1.4.2-SNAPSHOT Mojarra plugin support for reload of natively managed beans by JSF was added . However Jakarta faces 4.0 removed native managed bean support (jakartaee/faces#1547) . Solution is to practically revert to 1.4.1 version of Mojarra plugin, i did this by creating custom plugin in our project and disabled Mojarra plugin via properties file. |
Any news on this? |
No updates, any help with it would be greatly appreciated. |
Should be fixed in 1.4.2-SNAPSHOT release now. |
it is fixed in 1.4.1-SNAPSHOT |
The WeldJakarta plugin has been fixed, and most JUnit tests are now functioning correctly. |
Is support for jakarta packages planned ?
After migrating it keeps complaining like this :
11:22:46,238 INFO [stdout] (MSC service thread 1-6) Caused by: compile error: no such class: javax.enterprise.context.spi.Contextual
11:23:52,099 INFO [stdout] (ServerService Thread Pool -- 7) Caused by: compile error: no such class: javax.persistence.spi.PersistenceUnitInfo
Thank you in advance
The text was updated successfully, but these errors were encountered: