jfrog / jfrog/jfrog-cli-security
Gradle 9 Support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Describe the bug
What is the timeline for Gradle 9 support?
Current behavior
When running with a Gradle 9 wrapper, configurations need to be resolved exclusively which leads to the following error:
> Resolution of the configuration '...' was attempted without an exclusive lock. This is unsafe and not allowed.
Reproduction steps
jfrog audit --gradle ...
Expected behavior
No response
JFrog CLI version
2.79.2
Operating system type and version
Linux 6.8.0-84-generic jfrog/jfrog-cli#84~22.04.1-Ubuntu
JFrog Artifactory version
No response
JFrog Xray version
No response
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 jfrog audit --gradle ... entry point and inspect the Gradle integration involved in configuration resolution. Reproduce the failure with a Gradle 9 wrapper; done means the command no longer reports the exclusive-lock error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100