We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Jakarta Portlet project migrates the JSR 362 Specification and API from Java EE to Jakarta EE.
This is a good opportunity for Vaadin to support Vaadin Portlet add-on in Vaadin 24+ versions and let them work with Liferay.
Here are some links to follow: https://liferay.dev/blogs/-/blogs/liferay-s-java-roadmap-for-2025 https://liferay.dev/blogs/-/blogs/preparing-for-jakarta https://projects.eclipse.org/proposals/jakarta-portlet https://liferay.atlassian.net/browse/LPD-49394
Summary: Liferay Jakarta EE 10 migration timeline - Q3 2025, Java 17 is deprecated, Java 21 - full focus.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The Jakarta Portlet project migrates the JSR 362 Specification and API from Java EE to Jakarta EE.
This is a good opportunity for Vaadin to support Vaadin Portlet add-on in Vaadin 24+ versions and let them work with Liferay.
Here are some links to follow:
https://liferay.dev/blogs/-/blogs/liferay-s-java-roadmap-for-2025
https://liferay.dev/blogs/-/blogs/preparing-for-jakarta
https://projects.eclipse.org/proposals/jakarta-portlet
https://liferay.atlassian.net/browse/LPD-49394
Summary:
Liferay Jakarta EE 10 migration timeline - Q3 2025,
Java 17 is deprecated, Java 21 - full focus.
The text was updated successfully, but these errors were encountered: