redhat-developer / redhat-developer/vscode-java
The Ext always consider the direct build folder will located inside workplace folder
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Describe the bug
The Ext always consider the direct build folder will located inside workspace folder.
To Reproduce
Steps to reproduce the behavior:
So, if I set the following config in Pom.xml:
the Ext. will create [/x folder/builds/${project.artifactId}] inside the workspace directory and will use it for compiling.
[Please attach a sample project reproducing the error]
[Please attach logs. See https://github.com/redhat-developer/vscode-java/wiki/Troubleshooting#enable-logging]
Expected behavior
use the same folder that set in pom.xml.
I always set the build folder outside workspace folder to avoid OneDrive synch issues. and this settings working well with all IDEs and ext except this one.
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 extension reads the build directory from Pom.xml and resolves the configured path. Reproduce the issue with c:/x folder/builds/${project.artifactId} outside the workspace, then verify compilation uses that exact external directory rather than creating a workspace-relative folder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- build-system, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100