Reduce in-source gradle files
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
Logging a reminder to revisit the need to check in build support files such as gradle wrapper jars into the repo.
When originally setting this up, working in a hurry I have found the following CI setup instructions that seem to indicate it is common practice to keep the Gradle wrapper JARs checked in. It might not be the only way to do things though.
https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-java-with-gradle
"The "Validate Gradle wrapper" step validates the checksums of Gradle Wrapper JAR files present in the source tree."
Affected area/feature
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 by locating the repository's Gradle wrapper JARs and related build or CI configuration. Check the Gradle wrapper validation guidance referenced in the issue, then determine whether the files can be removed while builds and CI continue to work; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100