salesforce / salesforce/rules_spring
Support for the Spring Boot thin jar layout
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 257
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
Spring Boot has an experimental thin layout.A thin Spring Boot jar does not contain the dependencies internally like in the fat jar. The thin loader reads a descriptor (pom.xml or thin.properties) that then triggers the loader to download those dependencies at first launch of the service.
I am not wild about it because it runs contrary to the idea of the Bazel principle of producing a hermetic output. I see the value though - if you distribute your app widely, it reduces the size of the binary that you push to your users. If those users already have your deps in their .m2/repository, they won't have to incur the cost of downloading the fat jar with all of them.
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
Start by reviewing the repository's Bazel rule for building a deployable Spring Boot jar, then read the linked Spring Boot Thin Jar reference. Compare the current fat-jar behavior with the thin layout using pom.xml or thin.properties as the described dependency descriptor. Done should mean the rule supports producing the requested thin layout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spring-boot
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100