-
Notifications
You must be signed in to change notification settings - Fork 83
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
Fix system package launch validation #221
Fix system package launch validation #221
Conversation
@vik-chand do you want to review this? |
The list of system-packages in the <EE>-systempackages.profile file in o.e.pde.api.tools is not suitable for Launch-validation, query them from the VM instead. Fixes eclipse-pde#194
848dde5
to
84efc8f
Compare
I will review it by EOD today. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'll try removing the system-package in Y build and assuming launch with Java 19 works with the new code and adding a API baseline works without an error, then we could replace that code too in master stream. |
Opened #228 for the other case |
Thank you for reviewing Vikas. |
No it doesn't. But I strongly suspect that this has the same cause and can be fixed in the same way. When looking a bit if the API-profiles can be removed I noticed that PDE-Build uses them just like the launch validation did. So I think the same fix can be applied there. |
Created #284, can you test the PR if that also works in your use case? |
Use the actual VM system packages for Launch-Validation.
The list of system-packages in
o.e.pde.api.tools/system_packages/<EE>-systempackages.profile
files is not suitable for Launch-validation.Fixes #194.
Besides that I wonder if
ApiBaseline.getJavaProfilePropertiesForVMPackage()
could be replaced with the same method? This would also make creating thesystem_packages/<EE>-systempackages.profile
files obsolete.