jfrog / jfrog/jfrog-cli-security
Supporting Maven and Gradle Wrapper in JFrog Xray audit-gradle and audit-mvn
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
I am trying to execute JFrog Cli with the command
jfrog audit-gradle
I got and error below:
[Error] exec: "gradle": executable file not found in $PATH
It seems the jfrog cli relies on gradle on the path which may be installed as a system wide gradle installation.
Describe the solution you'd like to see
I prefer the jfrog cli for audit-gradle to support gradle wrapper. This can be extended to maven wrapper as well. Our environment doesn't have system wide installation of Gradle/Maven in the system $PATH.
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 audit-gradle and audit-mvn command entry points and reproduce the reported jfrog audit-gradle failure when Gradle is absent from PATH. Trace how each command invokes Gradle or Maven, then verify that project wrappers are used when available and that both audit commands work without system-wide installations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100