Updating lombok versions

[adrianmoya]

I was having issues with lombok, and decided to manually update the version by replacing the jar at /server. It looks like the issue disappeared. I was thinking maybe a config setting to set the path to the lombok jar could make it easier to get the latest version of lombok without depending on the plugin to be updated.

Thoughts?

[adrianmoya]

Or a version setting that the plugin can use to download the selected version. If there's interest I can try a PR with some guidance.

[chucknelson]

@adrianmoya It's been more than a year, so not sure if are still considering this, but this seems like a good idea.

I was thinking of the following:

• One goal should be get the .jar out of the repository
• It could download the latest version by default, allowing you to switch versions also, but...
• Ideally it would look into your project, look for the actual Lombok dependency you're using, and point to that .jar file. Not sure how this would interact with the extension activation, as this would have to happen before the vscode-java extension starts up...

[JoseLion]

IMHO making it look into the project and downloading the version of the actual Lombok dependency you're using could be a second iteration for this feature. It's an excellent idea, but it may be hard to make it work on any build tool (Maven, Gradle, etc.)

For starters, it would be extremely helpful for people using the plugin if they could at least choose the version they want to use in each project. We can store the selected version in .vscode\settings.json to have different versions for each project.

I think we could get some inspiration from vscode-checkstyle plugin, which already has this feature 🙂