WIP: enable javac-based compilation #3558
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fbricon
force-pushed
the
javac-poc
branch
2 times, most recently
from
5b55230
to
cb2d077
Compare
|
Daily vscode-javac builds are available from https://github.com/fbricon/vscode-java/releases/tag/javac-prototype |
Signed-off-by: Fred Bricon <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requires building eclipse.jdt.ls against dom-with-javac branch of the JDT fork
Requires running with Java 22 at the moment.
First build the server jars with:
then generate the vsix with:
Enable with
"java.jdt.ls.javac.enabled":"on"in vscode settingsSo far, it's pretty useless, since lots of work still needs to be done on the javac branch. You'll mainly be able to see the javac-generated compilation errors.
Completion, when it works, is still delegated to ECJ.