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
Enforce encapsulation of equinox-launcher Constants and JNIBridge #565
Enforce encapsulation of equinox-launcher Constants and JNIBridge #565
Conversation
Looks like at least the org.eclipse.launcher.tests introduced with #401, needs some adjustments. |
55c5963
to
4504ab2
Compare
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.
I can't say if I am confident that JNIBridge is not needed outside of the launcher by anyone. Regardless, I don't think it was ever intended to be API. We can move forward here I think.
...ure/library/org.eclipse.launcher.tests/src/org/eclipse/equinox/launcher/TestLauncherApp.java
Show resolved
Hide resolved
4504ab2
to
0b00fc8
Compare
0b00fc8
to
d490910
Compare
Ok, good. |
Not from me. |
Because JNIBridge is a package-private class since [1] it cannot be referenced from external bundles anyway. So there is no need for API-tags to prohibit that. [1] - eclipse-equinox#565
Because JNIBridge is now a package-private class it cannot be referenced from other bundles anyway. So there is no need for API-tags that prohibit it. Follow-up of eclipse-equinox#565
Because JNIBridge is now a package-private class it cannot be referenced from other bundles anyway. So there is no need for API-tags that prohibit it. Follow-up of #565
In the Eclipse SDK there are neither references to
org.eclipse.equinox.internal.launcher.Constants
nor toorg.eclipse.equinox.launcher.JNIBridge
.@tjwatson or anybody else are you aware of external users that need those two classes public at the places where they are?