-
Notifications
You must be signed in to change notification settings - Fork 8
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
OSGI Version Upgrade (support building on JDK 17 and JDK 21) #2943
Comments
[UPDATE]I have successfully built the caron-kernel 4.9.x branch using JDK 17, after resolving the issues that arose during the process. Next, I built the carbon-apimgt branch with the new carbon-kernel version and the new version of axis2, after addressing the encountered issues. I am currently working on resolving OSGI issues while building the product-apim branch with JDK 17 and the aforementioned new versions. |
[STATUS UPDATE]I am still working on resolving OSGI issues in product-apim build that arose after upgrading the kernel and carbon-apimgt versions, which were built with JDK 17. I was able to resolve the following issues in respective components to achieve a successful build status: P2 plugin requires the
Additionally, I made the required changes for |
[STATUS UPDATE]Added the required dependency version upgrades for the following branches so far. Some OSGi issues are still required to be fixed while building the product-APIM. The affected branches are:
|
[STATUS UPDATE]In progress building product APIM branch with JDK17, resolving the missing classes by adding the provide-capability tag to the identified code repositories. Tracked all the changes and PRs in [1]. [1] https://docs.google.com/spreadsheets/d/1ElOQFXoS1D6lSlxS_ROChEvBspTlgK0byhvkTerOEUQ/edit?usp=sharing |
[STATUS UPDATE]
|
[STATUS UPDATE]
|
Problem
Add support to building APIM on JDK 17 and JDK 21
Solution
OSGI Version Upgrade
Affected Component
APIM
Version
No response
Implementation
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: