redhat-developer / redhat-developer/vscode-java
Setting java.import.gradle.home in multi-project structure via vscode variable
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
I have a gradle multi-project structure in which the gradle wrapper is only placed in the root project.
Since I want all sub-projects to use the same wrapper (and not e.g. my local installation) I set the java.import.gradle.home in my workspace settings.
Ideally, I want to set this variable as: java.import.gradle.home=${workspaceFolder}/.gradle/...
However, in the generated .settings/org.eclipse.buildship.core.prefs in the subprojects I can see that the path is only copied and the vscode variable ${workspaceFolder} is not expanded.
Is it possible to support vscode variable expansion in the extension?
Are there other ways to set the gradle wrapper path relative to the project path? Currently, I am using the absolute path in my settings file. However, this would need to be updated by other team members.
Environment
- Operating System: macOS
- JDK version: 1.11
- Visual Studio Code version:1.45.1
- Java extension version: 0.62.0
Steps To Reproduce
- Create gradle multi-project
- Set
java.import.gradle.homeusing${workspaceFolder}
Current Result
Vscode variables (e.g. ${workspaceFolder}) used for e.g. java.import.gradle.home are not expanded in the org.eclipse.buildship.core.prefs (hence throwing no such file exception)
Expected Result
Vscode variables are correctly expanded and correct path is shown in org.eclipse.buildship.core.prefs of the subprojects
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 tracing how the java.import.gradle.home setting is handled when generating .settings/org.eclipse.buildship.core.prefs for Gradle subprojects. Reproduce the multi-project setup with ${workspaceFolder} and inspect the generated preference path. Done means the variable is expanded and the subprojects reference the root project's wrapper path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100