jfrog / jfrog/jfrog-cli-security
jf audit doesn't support passing of additional arguments to gradle
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Hello ,
jf.exe audit command doesn't support passing of additional arguments to package manager tools like:
Maven, gradle.
there are many cases where if we would require to pass additional arguments that maven and gradle supports . Otherwise, the build would fail. Eventually, jf audit would also fail. Could you please consider this as a feature-request?
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 jf audit command entry point and trace how it invokes Maven and Gradle package-manager tools. Determine how additional arguments are represented and forwarded, then verify that builds requiring those arguments can complete audit successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100