Could not find lombok.jar path

[ancion]

Problem : Could not find lombok.jar path

----  client.log ------------------------------
2023-01-30T10:08:17.069 INFO (pid:5376) - Use the JDK from 'java.jdt.ls.java.home' setting as the initial default project JDK.
2023-01-30T10:08:17.260 WARN (pid:5376) - Could not find lombok.jar path.
2023-01-30T10:08:17.301 INFO (pid:5376) - Starting Java server with: F:\jdk17\bin\java --add-modules=ALL-SYSTEM --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/sun.nio.fs=ALL-UNNAMED -Declipse.application=org.eclipse.jdt.ls.core.id1 -Dosgi.bundles.defaultStartLevel=4 -Declipse.product=org.eclipse.jdt.ls.core.product -Djava.import.generatesMetadataFilesAtProjectRoot=false -Dfile.encoding=UTF-8 -Xlog:disable -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\Users\unicorn\AppData\Local\coc\extensions\coc-java-data -jar C:\Users\unicorn\AppData\Local\coc\extensions\node_modules\coc-java\server\plugins\org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar -configuration C:\Users\unicorn\AppData\Local\coc\extensions\coc-java-data\1.14.0\config_win -data C:\Users\unicorn\AppData\Local\coc\extensions\coc-java-data\jdt_ws
2023-01-30T10:08:17.425 INFO (pid:5376) - WARNING: Using incubator modules: jdk.incubator.foreign, jdk.incubator.vector
---------------------------------------------------------------------

"coc-java" configuration

this should be work with java.jdt.ls.vmargs: "-javaagent:/path/to/lombok.jar" in earlier version. but now it looks like not load this option.

{
   "java.jdt.ls.vmargs": "-javaagent:/path/to/lombok.jar"
} 

Where should I put "lombok.jar" ?

[bertin0]

I also faced during my exam today after I updated without testing the update, but i'm still not sure if it's a jdt.ls issue or something else related to lombok as I can't build stuff with it even with maven.

[alprogs]

I've also faced this issue too..
It seems to be the '-javaagent' was disappeared when starting java server.

[amgodoi]

Same problem.
Any workaround?

[alprogs]

I didn't see the code in detail, but I can check that I copied lombok.jar to the path below and confirmed that it can be referenced in coc-java.

$ ls ~/.config/coc/extensions/node_modules/coc-java/lombok/lombok.jar
/home/brad/.config/coc/extensions/node_modules/coc-java/lombok/lombok.jar

[Stark-X]

coc-java/src/lombokSupport.ts

Lines 130 to 149 in 1470028

	for (const projectUri of projectUris) {
	const classpathResult = await apiManager.getApiInstance().getClasspaths(projectUri, { scope: 'test' })
	for (const classpath of classpathResult.classpaths) {
	if (lombokJarRegex.test(classpath)) {
	currentLombokClasspath = classpath
	if (activeLombokPath && !isExtensionLombok) {
	currentLombokVersion = lombokJarRegex.exec(classpath)[0]
	previousLombokVersion = lombokJarRegex.exec(activeLombokPath)[0]
	if (currentLombokVersion !== previousLombokVersion) {
	versionChange = true
	}
	}
	lombokFound = true
	break
	}
	}
	if (lombokFound) {
	break
	}
	}

it seems that there is a new feature to find out the lombok class in the project class path, but something wrong.

How could i write test for the feature or debug that?

[ancion]

I didn't see the code in detail, but I can check that I copied lombok.jar to the path below and confirmed that it can be referenced in coc-java.

$ ls ~/.config/coc/extensions/node_modules/coc-java/lombok/lombok.jar /home/brad/.config/coc/extensions/node_modules/coc-java/lombok/lombok.jar

this should be work in my windows 11. The coc dictionary is c:/user/name/AppData/Local/coc.
add version lombok.jar --> lombok-${version}.jar could be work well, otherwise get an [coc.error].

[sify21]

Confirmed move lombok.jar to ~/.config/coc/extensions/node_modules/coc-java/lombok/lombok-{version}.jar fix the problem, and no need to configure lombok through java.jdt.ls.vmargs. I'm on Mac.

[trev-dev]

I had a look at the upstream vscode extension and found this little diddy: redhat-developer/vscode-java#2887 (comment)

Following guidance from there, I set this up:

{
  "java.jdt.ls.lombokSupport.enabled": false,
  "java.jdt.ls.vmargs": "-javaagent:${env:LOMBOK_JAR} -XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xmx1G -Xms100m -Xlog:disable",
}

I have proper lombok support now. Note that ${env:LOMBOK_JAR} is set by nixos in my case, you can go ahead and use an absolute path instead.