Support Kotlin,Groovy in Gradle projects by snjeza · Pull Request #3682 · eclipse-jdtls/eclipse.jdt.ls

snjeza · 2026-01-21T00:44:06Z

Addresses redhat-developer/vscode-java#4312
linked to redhat-developer/vscode-java#4313

fbricon · 2026-01-21T09:13:44Z

So it seems that if, after a kotlin project has been imported, if I create a new kt file, e.g. App2.kt, a copy of App.kt, and then reference it in the java file (new App2().hello();), compilation still fails.
Restarting vscode doesn't fix it. You need to clean the java language server workspace to trigger a full reimport, in order for compilation to be fixed.

fbricon

adding new Kotlin or Groovy files, or adding new methods to existing ones are not visible to the java compiler, until a full reimport occurs

fbricon · 2026-01-21T09:19:25Z

org.eclipse.jdt.ls.tests/projects/gradle/groovy/src/main/groovy/org/sample/Demo.java

@@ -0,0 +1,10 @@
+package org.sample;


should prolly go into src/main/java

I have tried it, but the compileGroovy task depends on the compileJava task, which compiles the Java source before the Groovy source, and can't find the App class. It fails from the Gradle command line.

fbricon · 2026-01-21T09:20:06Z

org.eclipse.jdt.ls.tests/projects/gradle/groovy/src/build.gradle

@@ -0,0 +1,22 @@
+apply plugin: "io.freefair.aspectj"


file should be deleted

fbricon · 2026-01-21T09:20:40Z

org.eclipse.jdt.ls.tests/projects/gradle/kotlin/src/build.gradle

@@ -0,0 +1,22 @@
+apply plugin: "io.freefair.aspectj"


file should be deleted

snjeza · 2026-01-21T17:02:05Z

So it seems that if, after a kotlin project has been imported, if I create a new kt file, e.g. App2.kt, a copy of App.kt, and then reference it in the java file (new App2().hello();), compilation still fails.
Restarting vscode doesn't fix it. You need to clean the java language server workspace to trigger a full reimport, in order for compilation to be fixed.
adding new Kotlin or Groovy files, or adding new methods to existing ones are not visible to the java compiler, until a full reimport occurs

If you change a Groovy or Kotlin class, you will need to reload the root project for the changes to be visible when running the tests. We could add *.kt and *.groovy files to VS Code watchers if the Groovy and Kotlin preferences are enabled.

fbricon · 2026-01-22T16:06:12Z

If you change a Groovy or Kotlin class, you will need to reload the root project for the changes to be visible when running the tests. We could add *.kt and *.groovy files to VS Code watchers if the Groovy and Kotlin preferences are enabled.

Sounds like it's gonna be pretty slow no? if you rebuild on each kt change

snjeza · 2026-01-22T20:42:26Z

Sounds like it's gonna be pretty slow no? if you rebuild on each kt change

Gradle supports incremental build - https://docs.gradle.org/current/userguide/incremental_build.html
I could try to run only the classes task.

fbricon · 2026-01-24T10:15:49Z

Gradle supports incremental build - docs.gradle.org/current/userguide/incremental_build.html I could try to run only the classes task.

let's see how it goes

snjeza · 2026-01-24T19:46:23Z

...I could try to run only the classes task.

let's see how it goes

I have added this feature.
You can test

fbricon · 2026-01-26T10:59:43Z

...lipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/managers/StandardProjectsManager.java

+					if (preferenceManager.getPreferences().isAutobuildEnabled() && ProjectUtils.isGradleProject(project)) {
+						if ((preferenceManager.getPreferences().isAspectjSupportEnabled() && resource.getName().endsWith(".aj")) || (preferenceManager.getPreferences().isKotlinSupportEnabled() && resource.getName().endsWith(".kt"))
+								|| (preferenceManager.getPreferences().isGroovySupportEnabled() && resource.getName().endsWith(".groovy"))) {


ProjectUtils.isGradleProject(project)) {
if ((preferenceManager.getPreferences().isAspectjSupportEnabled() && resource.getName().endsWith(".aj")) || (preferenceManager.getPreferences().isKotlinSupportEnabled() && resource.getName().endsWith(".kt"))

all that Gradle specific stuff should be moved down some IBuildSupport.shouldCompile(...) method. I'd rather prefer we avoided more build specific coupling in the managers

snjeza · 2026-01-26T22:14:17Z

@fbricon I have updated the PR.

snjeza · 2026-01-29T17:43:53Z

@fbricon I have updated the PR.

snjeza · 2026-01-31T18:46:53Z

I have added the following improvements:

if a groovy project contains compile errors, the build won’t fail
if there are compile errors in AspectJ, Groovy, Kotlin projects, they will appear when VS Code is started for the first time

snjeza · 2026-02-01T20:12:20Z

test this please

snjeza · 2026-02-02T14:58:49Z

test this please

snjeza mentioned this pull request Jan 21, 2026

Support Kotlin,Groovy in Gradle projects redhat-developer/vscode-java#4313

Open

snjeza force-pushed the issue-4312 branch from d560bb9 to bfab9fd Compare January 21, 2026 04:58

fbricon mentioned this pull request Jan 21, 2026

kotlin imports into Java file are unresolved redhat-developer/vscode-java#531

Open

fbricon requested changes Jan 21, 2026

View reviewed changes

snjeza force-pushed the issue-4312 branch from bfab9fd to b9e1c59 Compare January 21, 2026 17:06

snjeza force-pushed the issue-4312 branch from b9e1c59 to 87616ad Compare January 24, 2026 19:40

snjeza force-pushed the issue-4312 branch from 87616ad to dda8918 Compare January 24, 2026 19:53

fbricon requested changes Jan 26, 2026

View reviewed changes

snjeza force-pushed the issue-4312 branch from dda8918 to f157eb7 Compare January 26, 2026 22:12

snjeza force-pushed the issue-4312 branch from f157eb7 to 1395a42 Compare January 29, 2026 17:35

snjeza force-pushed the issue-4312 branch 2 times, most recently from a5a2295 to 650941d Compare January 31, 2026 18:44

snjeza force-pushed the issue-4312 branch from 650941d to b8a2374 Compare February 1, 2026 21:55

Support Kotlin,Groovy in Gradle projects

f528f3b

snjeza force-pushed the issue-4312 branch from b8a2374 to f528f3b Compare February 2, 2026 18:32

This comment was marked as spam.

Sign in to view

Conversation

snjeza commented Jan 21, 2026 • edited by fbricon Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

fbricon commented Jan 21, 2026

Uh oh!

fbricon left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

snjeza commented Jan 21, 2026

Uh oh!

fbricon commented Jan 22, 2026

Uh oh!

snjeza commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

fbricon commented Jan 24, 2026

Uh oh!

snjeza commented Jan 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

snjeza commented Jan 26, 2026

Uh oh!

snjeza commented Jan 29, 2026

Uh oh!

snjeza commented Jan 31, 2026

Uh oh!

snjeza commented Feb 1, 2026

Uh oh!

snjeza commented Feb 2, 2026

Uh oh!

This comment was marked as spam.

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

snjeza commented Jan 21, 2026 •

edited by fbricon

Loading

snjeza commented Jan 22, 2026 •

edited

Loading

snjeza commented Jan 24, 2026 •

edited

Loading