`java.import.gradle.user.home` Setting not Respected
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- java, typescript, vscode
- Domain
- build-system, developer-experience
Research direction
Start by reproducing the issue with GRADLE_USER_HOME and java.import.gradle.user.home set as described, then trace how the Java extension pack passes Gradle settings to Gradle processes. Done means Gradle processes use the configured cache location rather than the default .gradle path, including when the setting is defined at project level.
Written by the indexing model from the issue text.
Description
Environment
- VS Code Version:
1.99.22418(Flatpak build) - Extension Version:
vscjava.vscode-java-pack 0.29.0 - JDK Type & Version:
Eclipse Temurin 21.0.7+6.0.LTS - OS Type & Version:
GNU/Linux x64 6.12.23-1-lts #1 SMP PREEMPT_DYNAMIC
Step to Reproduce
- Set
GRADLE_USER_HOMEenvironment variable within the operating system —GRADLE_USER_HOME="/path/to/user-home/.cache/gradle" - Set
"java.import.gradle.user.home": "/path/to/user-home/.cache/gradlein globalsettings.json - Create/Open a Gradle project
Expected Behavior
Gradle processes should use the correct location defined by java.import.gradle.user.home.
Actual Behavior
Gradle processes still default to /path/to/user-home/.gradle
Additional Information
I've also tried to set java.import.gradle.user.home in settings.json at the project level.
- Dominant language
- TypeScript
- Stars
- 352
- Forks
- 166
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 32
Contributor guide
No contributing guide indexed for this repository
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.
More from microsoft/vscode-java-pack
-
Memory Leak in Linux Openai-triaged bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/vscode-java-pack#1543 · 8 comments · 4 reactions ·
-
ai-triaged bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/vscode-java-pack#1443 · 1 comment · 2 reactions ·
-
ai-triaged enhancement feature-request
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/vscode-java-pack#1423 · 2 comments · 1 reaction ·
-
ai-triaged area/jdtls bug needs-investigation
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/vscode-java-pack#1420 · 1 comment ·
-
java.project.sourcePaths Setting Fails to Exclude Test Directory from References and Call Hierarchy Openai-triaged bug language-server
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/vscode-java-pack#1408 · 1 comment ·
All issues in microsoft/vscode-java-pack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·