Regression on 1.41.0 - Given URI does not belong to an existing Java source file.

[lmajano]

I just updated to the latest version 1.41.0 and now the plugin doesn't parse any java files in my gradle project. If you revert to 1.40.0 then, it resolves itself.

Here is the stacktrace:

Given URI does not belong to an existing Java source file.
org.eclipse.core.runtime.CoreException: Given URI does not belong to an existing Java source file.
	at org.eclipse.jdt.ls.core.internal.commands.ProjectCommand.isTestFile(ProjectCommand.java:445)
	at org.eclipse.jdt.ls.core.internal.JDTDelegateCommandHandler.executeCommand(JDTDelegateCommandHandler.java:109)
	at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler$1.run(WorkspaceExecuteCommandHandler.java:230)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
	at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler.executeCommand(WorkspaceExecuteCommandHandler.java:220)
	at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$4(JDTLanguageServer.java:616)
	at org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:87)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool.scan(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)

No matter which Java file it opens, this is the same in the logs, and then all the features of the extension are crippled: test explorer, references, etc.

The only way to fix it, is by reverting to 1.40.0

To replicate, clone our project: https://github.com/ortus-boxlang/boxlang
Then open it in the extension, wait for it to load, and open any Java file.

[rgrunber]

Are you using the "Gradle for Java" extension as well ? Is java.gradle.buildServer.enabled set to "on" or "off" ?

[lmajano]

I am using the extension pack:

and Here are my settings:

[rgrunber]

I think I'm able to reproduce the issue, so at least I can investigate it. My guess is it's something in https://github.com/microsoft/vscode-gradle/ .

[rgrunber]

Can you try the latest pre-release build of vscode-java, v1.42.2025040104. I think it should contain the fix for this issue. Might be the same problem as #3995 .

[lmajano]

Thanks @rgrunber I will try this afternoon and report back. Great work!

[rgrunber]

Closing this for now as I'm sure this would have fixed things. I specifically used boxlang to test. Feel free to re-open if it doesn't appear to be solved but there are about 2 other known issues that need fixes in vscode-gradle, and vscode-java-test that are being worked on. See #3995 (comment)

[lmajano]

Sorry. Been swamped. Will reopen if it fails but will test tonight. Luis Majano CEO Ortus Solutions, Corp 1-888-557-8057 909-248-3408 www.ortussolutions.com www.boxlang.io www.luismajano.com Support Open Source: www.patreon.com/ortussolutions Linked In: https://www.linkedin.com/pub/3/731/483 Social: twitter.com/ortussolutions | twitter.com/lmajano | bsky.app/profile/lmajano.bsky.social El 2 abr 2025, 15:11 +0200, Roland Grunberg ***@***.***>, escribió:

…

Closing this for now as I'm sure this would have fixed things. I specifically used boxlang to test. Feel free to re-open if it doesn't appear to be solved but there are about 2 other known issues that need fixes in vscode-gradle, and vscode-java-test that are being worked on. See #3995 (comment) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> rgrunber left a comment (redhat-developer/vscode-java#3998) Closing this for now as I'm sure this would have fixed things. I specifically used boxlang to test. Feel free to re-open if it doesn't appear to be solved but there are about 2 other known issues that need fixes in vscode-gradle, and vscode-java-test that are being worked on. See #3995 (comment) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[lmajano]

Ok it's working. Confirmed. 1. Update the extensions to the pre-release 2. Clear and reload the Java Workspace 3. Restart Luis Majano CEO Ortus Solutions, Corp 1-888-557-8057 909-248-3408 www.ortussolutions.com www.boxlang.io www.luismajano.com Support Open Source: www.patreon.com/ortussolutions Linked In: https://www.linkedin.com/pub/3/731/483 Social: twitter.com/ortussolutions | twitter.com/lmajano | bsky.app/profile/lmajano.bsky.social

…

On Apr 1, 2025 at 06:30 +0200, Roland Grunberg ***@***.***>, wrote: Can you try the latest pre-release build of vscode-java, v1.42.2025040104. I think it should contain the fix for this issue. Might be the same problem as #3995 .