salesforce / salesforce/rules_spring
Enable compression on resources in primary jar
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 257
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
Springboot forbids compression nested jars/archives, however, it does not (to my knowledge) forbid compression assets in the top-level jar. This rule set does disables all the compression on the final artifact, which can result in much higher archive sizes compared to the same application built in gradle for example.
It would be helpful to only disable compression on jars within the top level jar.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no implementation files or tests; start by locating the rule that builds the deployable Spring Boot jar and its archive-compression tests or entry points. Verify that nested jars remain uncompressed while resources in the top-level jar are compressed, then run the relevant tests and compare the resulting archive behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spring-boot
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100