redhat-developer / redhat-developer/vscode-java
If wrapper is disabled, Gradle import should prefer the one on the Path over the embedded one
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
With "java.import.gradle.wrapper.enabled": false, the import prefers the embedded Gradle over the Gradle on the Path. This is counterintuitive and leads to errors: currently the embedded Gradle is 7.1.1, which is unable to import JDK 17 projects.
I know that I can set java.import.gradle.home, but that is merely a workaround.
Environment
- Operating System: Windows 11
- JDK version: 17.0.2
- Visual Studio Code version: 1.65.2
- Java extension version: 1.4.0
Steps To Reproduce
- have Gradle 7.3.1+ on the Path
- set
"java.import.gradle.wrapper.enabled": false - import a JDK 17-based Gradle project
Current Result
Fails with an error related to the embedded Gradle
Expected Result
Succeeds because the Gradle on the Path is preferred over the embedded Gradle
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Gradle import with java.import.gradle.wrapper.enabled set to false, Gradle 7.3.1 or newer on PATH, and a JDK 17-based project. Trace the Gradle selection entry point and verify that the PATH installation is selected instead of the embedded Gradle, then confirm the project imports successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100