jfrog / jfrog/jfrog-cli-security
jf audit and maven parameters
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.
Currently, the jf cli doesn't have the capability to add maven custom parameters during a jf audit --mvn command.
This if frustrating because for specific projects like talend project, we often pass parameters for maven commands.
Describe the solution you'd like to see
jf audit --mvn has the capability to get additional maven goals.
The mvn.go in the jfrog-cli-core have already a set of goals and parameters ("-B", "compile", "test-compile"). It should be possible to pass an additional array of strings containing the custom parameters.
Describe alternatives you've considered
Additional context
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 with the jf audit --mvn command and the linked xray/audit/java/mvn.go entry point in jfrog-cli-core, then trace how Maven goals and parameters are assembled. Define how an additional string array reaches the audit command and verify that custom Maven parameters are included alongside the existing -B, compile, and test-compile arguments.
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
- Mostly clear
- Newbie friendliness
- 38/100