You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was off for a couple of weeks, when I came back I updated the OS + VSCode + Java extension to the latest version. Then VSCode refused to start the Java Language Server workspace...
Reading the logs, the extension was selecting the Java Applet Plugin (yes, that thing from 2000) to start the Java server?!? It failed because these java binaries are for Intel x64, and Golden Gate won't run these anymore.
I double-checked my java.jdt.ls.java.home settings (correctly pointing to Java 25), I checked my $JAVA_HOME (ditto). I googled (no dice).
In the end I had to sudo and delete the Java applet plugin in /Library; then I had to delete the JDK 1.8 because the extension was picking that one instead; then I had hack a javaws link... Right now it works, and it seems to be using the right JVM.
And then I had to revert to version 1.56 of the extension anyway, because 1.58 broke(?) Lombok @Nullable in record types: it throws errors that final fields have not been initialized 🫠 . The code compile in 1.56, so there's a regression somewhere. That's on top of (known) bug where it ignores the lombok.copyJacksonAnnotationsToAccessors settings...
Part of it may be due to running a 5-year-old computer that has gone through 4 major OS upgrades. But every new extension version brings its lot of disruption; just not the positive kind...
Anyway, if you also ran into this issue and have a better solution lmk.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I was off for a couple of weeks, when I came back I updated the OS + VSCode + Java extension to the latest version. Then VSCode refused to start the Java Language Server workspace...
Reading the logs, the extension was selecting the Java Applet Plugin (yes, that thing from 2000) to start the Java server?!? It failed because these java binaries are for Intel x64, and Golden Gate won't run these anymore.
I double-checked my
java.jdt.ls.java.homesettings (correctly pointing to Java 25), I checked my$JAVA_HOME(ditto). I googled (no dice).In the end I had to sudo and delete the Java applet plugin in
/Library; then I had to delete the JDK 1.8 because the extension was picking that one instead; then I had hack ajavawslink... Right now it works, and it seems to be using the right JVM.And then I had to revert to version 1.56 of the extension anyway, because 1.58 broke(?) Lombok
@Nullableinrecordtypes: it throws errors that final fields have not been initialized 🫠 . The code compile in 1.56, so there's a regression somewhere. That's on top of (known) bug where it ignores thelombok.copyJacksonAnnotationsToAccessorssettings...Part of it may be due to running a 5-year-old computer that has gone through 4 major OS upgrades. But every new extension version brings its lot of disruption; just not the positive kind...
Anyway, if you also ran into this issue and have a better solution lmk.
All reactions