Why shaded?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 176
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Why has guava and paranamer been shaded in? This makes this otherwise pretty lightweight library bloated and at least for myself makes it less desirable to re-use over re-implementation.
I get that some folks it may be simpler with a single jar, but in that case a shaded "attached" artifact may be simpler, and leaves those that already have rigid controls over dependencies the flexibility to use the library with-out the shaded inflation.
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
Review the build configuration and published artifacts to identify where Guava and Paranamer are shaded into the library. Compare the current single-jar approach with the proposed separate shaded artifact, then check the issue discussion for maintainer direction. Done requires an agreed dependency-packaging outcome and corresponding artifact behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100