Skip to content
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

cherry pick commits which solve the lombok's getter setter issue for java8 #1724

Closed
howel52 opened this issue Apr 13, 2021 · 5 comments
Closed
Labels

Comments

@howel52
Copy link

howel52 commented Apr 13, 2021

The latest version of vscode-java that supports java8 is [email protected]

The [email protected] depends on [email protected]

And we found the same problem with #1548 in [email protected](commit sha: be8e636)

Then I cherry pick some commits into [email protected], fixed the problem.

Do we need to publish the [email protected] to support java 8 ? Something I did like this: howel52#1

: )

@fbricon
Copy link
Contributor

fbricon commented Apr 13, 2021

Any version < 1.0 are unsupported.
I'm not expecting we provide any backports for such an "old" version

@howel52
Copy link
Author

howel52 commented Apr 13, 2021

@fbricon

Okay, but how do we make the [email protected] fix the 'getter, setter' issue for java 8.

I think the [email protected] is the last version that supports java 8.

@rgrunber
Copy link
Contributor

rgrunber commented Apr 13, 2021

You would need to clone eclipse.jdt.ls , check out the 0.58.0 tag, and cherry-pick those commits onto that tag, which you seem to have done. From there, you would clone vscode-java (under the same parent directory as eclipse.jdt.ls), check out the 0.64.1 tag, run npm install followed by npm run build-server, and vsce package (need vsce installed) . The resulting vsix should contain a language server with the desired support.

@howel52
Copy link
Author

howel52 commented Apr 14, 2021

@rgrunber
My current solution is the same as you said, but it means I need to fork jdt.ls and maintain it.

@howel52 howel52 changed the title cherry pick commits which solve the lombok's getter setter isuue for java8 cherry pick commits which solve the lombok's getter setter issue for java8 Apr 14, 2021
@rgrunber
Copy link
Contributor

Yup, that's probably the best way to do it for now.

It's difficult to continue to support older versions with minimal effort when underlying dependencies are updating, partly due to finding it difficult to maintain older Java 8 support.

Closing this as there seems to be an agreed upon way to go about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants