redhat-developer / redhat-developer/vscode-java
Feature Request: configurable `defaultOutputDir` instead of hardcoded `bin`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Feature Request
Please provide a configuration to change defaultOutputDir bin
Detail
I'm not an eclipse user, as I know, bin is widely used as a dir that stores shell scripts, but vscode java plugin uses it as the default output dir, and can not be changed by configuration, the only way I know is using gradle eclipse plugin to generate .classpath with modified config by groovy script in build.gradle, see #634
buildDir = "build/gradle"
apply plugin: 'java'
apply plugin: 'eclipse'
eclipse {
classpath {
defaultOutputDir = file('build/eclipse')
file.whenMerged {
entries.each { entry ->
if (entry.kind == 'src' && entry.hasProperty('output')) {
entry.output = entry.output.replace('bin/', "build/eclipse/")
}
}
}
}
}
@jdneo https://github.com/redhat-developer/vscode-java/issues/2801#issuecomment-1318256946
You can vote for https://github.com/redhat-developer/vscode-java/issues/1615 to help us prioritize.
If anyone encounter this issue, please comment / give 👍 / link related issue to this one, to help the team escalate the priority of this issue.
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
The issue names no source files, tests, or entry points; begin by locating the code that sets the Java extension's hardcoded bin default and review existing configuration handling. Done means users can configure defaultOutputDir without the Gradle workaround, with coverage for the configured output path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- build-system, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100