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
Update documentation for javax -> jakarta migration #232
Comments
I have a pretty busy week this week. I'll try to tackle this over the weekend. In which document am I adding this? I have one remaining issue with my migration and this is more with using returning jaxb annotated classes in jaxrs annotated REST endpoints. While this is not related to the plugin, it is part of the the migration of my app and it might help others if I can figure out the right recipe for deps to get it all to work. |
I finally got my last problem solved. it's now fully java17 yay. the version of resteasy in wildfly 26, v4.7.4, doesn't deal with the jakarta classes fully yet, that' not until v5 of resteasy. I end up implementing a simple workaround. I'm just waiting on bitnami/wildfly docker image to be updated to be java17. They were helpful and told me how to build my own that was based on java17 so I could test. Were you wanting me to update the wiki? |
Any progress on this? |
I did end up getting things working. See my comments in the following issue What I needed to do to get it working my case is documented there. The switch to 17 in general was a bit of a pain since a lot of thing besides are in that half-pregnant state. I found the javax.mail to jakarta.mail migration to be problematic also. I'm expecting things to get easier as more frameworks and libs are updated. |
v4.0.0 being prepared for release. Leaving this open to adjust documentation as needed. Plan to close this ticket out in v4.0.1 |
We need to update the documentation to support two sections:
javax
jakarta
The text was updated successfully, but these errors were encountered: