Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Loading a gradle project in VS code results in Kotlin DSL accessors in the wrong directory: `bin/main/gradle/kotlin/dsl/`

Open
#1,435 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, kotlin, typescript, vscode
Domain
build-system, devtools

Research direction

No source file or test is named. Reproduce the issue by loading the linked idiomatic-gradle project with Gradle 8.5 and the VS Code Gradle extensions, then trace the project-loading path that places Kotlin DSL accessors under bin/main. Done means generated accessors and other build output remain under the Gradle build directory, such as build/generated-sources/kotlin-dsl-accessors.

Written by the indexing model from the issue text.

Description

ai-triaged bug

Loading a gradle project in VS code results in Kotlin DSL accessors in the wrong directory: bin/main/gradle/kotlin/dsl/

Environment
  • Operating System: macOS 13.6.2
  • JDK version: 17
  • Visual Studio Code version: 1.86.0
  • Java extension version: v0.25.15
  • Java Debugger extension version: 0.56.0
Steps To Reproduce
  1. load an gradle 8.5 project that uses *.gradle.kts files and included builds. e.g. this project: https://github.com/jjohannes/idiomatic-gradle/
  2. load it with the VS code gradle extensions.
Current Result

The kotlin DSL accessors are generated into bin/main/gradle/kotlin/dsl/ instead of the normal build/generated-sources/kotlin-dsl-accessors/kotlin/gradle/kotlin/dsl/ location.

Expected Result

all the build output is in the Gradle configure build out directory ( /build by default)

Additional Informations

Using Gradle 8.5

Possibly related issues
Dominant language
TypeScript
Stars
591
Forks
429
Avg merge
1d 9h
Merged PRs (30d)
19

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-java-debug

All issues in microsoft/vscode-java-debug

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.