-
Notifications
You must be signed in to change notification settings - Fork 145
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
Using internals which may not be visible #738
Comments
@cdietrich / @dhuebner looking for a second opinion - is this serious enough that we should do a quick next release? If we (collectively) can fix it immediately then I can do the release ASAP. |
what i dont understand. why is this not seen in tests. we run non osgi tests |
i also would prefer a .1 release otherwise we would need a new xtext release |
i am also not aware of people using lsp4j in osgi context |
Without OSGi the LSP4J can access that class (I think? as I don't know how JPMS fits in to the picture, if at all) On more reflection I don't think this is critical, just annoying as it means LSP4J is forcing LSP4E to use the Orbit gson. We should aim to fix soon, but I don't think we need to respin for this. |
It’s not critical. Next normal release will be soon enough. |
1 similar comment
It’s not critical. Next normal release will be soon enough. |
Thank you @merks for weighing in and giving me that confirmation! |
@jonahgraham |
@jonahgraham |
I asked Wayne Beaton review this because I was concerned about the copying but his assessment is in this case it is fine. |
In MessageTypeAdapter we are using an internal Gson type that is exported in Orbit's gson rebundling (as x-internal) but not in the manifest of the upstream gson.
lsp4j/org.eclipse.lsp4j.jsonrpc/src/main/java/org/eclipse/lsp4j/jsonrpc/json/adapters/MessageTypeAdapter.java
Line 46 in e32c63b
This forces consumers of jsonrpc (within an OSGi runtime) to use the Orbit version.
The text was updated successfully, but these errors were encountered: