-
Notifications
You must be signed in to change notification settings - Fork 148
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
Add module-info to the modules #830
Comments
Totally agree. BSL Language Server is packaged via jpackage and runtime image is quite huge. |
I will be happy to review a PR that provides the needed info. Please tag me in such a PR. |
maybe there is something that makes buildship configure the module thing correctly |
We would like to release 0.24.0, but we need to resolve or revert this change before we can do that. @Thihup are you able to review the issue raised in #855 so we can proceed? |
Hi. I am currently unable to fix it. Reverting it is fine for me. |
This reverts commit 7ce4f59 which was part of PR eclipse-lsp4j#843 This reversion is being done because the added module info breaks development setup and as of now no one has wanted to pickup the work of having module-info. By reverting this commit we can release 0.24.0 with the same metadata as 0.23.0 was released. Part of eclipse-lsp4j#830
This reverts commit 7ce4f59 which was part of PR #843 This reversion is being done because the added module info breaks development setup and as of now no one has wanted to pickup the work of having module-info. By reverting this commit we can release 0.24.0 with the same metadata as 0.23.0 was released. Part of #830
Adding a module-info to the modules will make the life easier for whom wants to create a JLinked runtime including only the necessary modules. Most LSP servers are standalone programs, so it makes sense to create a LSP server using a JLinked runtime.
The text was updated successfully, but these errors were encountered: