redhat-developer / redhat-developer/vscode-java
`Java: Import Java Projects into Workspace` ignores build tool conflict choice
Open
Nobody has claimed this yet.
bug
extension-start
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
steps to reproduce:
- git clone https://github.com/spring-projects/spring-petclinic
- vscode-java shows there is build tool conflict, choose Maven
- After importing, execute command
Java: Import Java Projects into Workspace - After importing, you can find the project is imported as Gradle project, and in
Java Projectsview it showsProject and External Dependencies(buildship style)
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
Reproduce the issue with spring-petclinic, selecting Maven when vscode-java reports the build tool conflict, then run Java: Import Java Projects into Workspace. Trace the import and conflict-choice handling; done means the selected Maven choice is respected and the project no longer appears as a Gradle or Buildship-style project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- build-system, developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100