redhat-developer / redhat-developer/vscode-quarkus
Improve error handling when Maven and Gradle wrapper does not have execute permissions
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- TypeScript
- Stars
- 79
- Forks
- 31
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 6
Description
When the Quarkus: Add extension to current project command is called while the ./mvnw or ./gradlew file does not have execute permissions, it is not possible to add extensions with the command:
Maven:
Gradle:
It would be great if vscode-quarkus could detect this, and try mvn or gradle instead of ./mvnw or ./gradlew.
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 at the implementation of the Quarkus: Add extension to current project command and trace how it invokes ./mvnw and ./gradlew. Reproduce the failure with execute permissions removed, then verify that the command can fall back to mvn or gradle and still add the extension.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100