Eclipse collections dependency
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.1k
- Forks
- 877
- PR merge metrics
- No merged PRs in 30d
Description
I just went through all dependencies for my application, and eclipse-collections stands out with whopping 10.2 MB, or about the third of my total application size. And if I tracked it down correctly, this dependency got included because I use MapDB. Is there any way to get rid of it? I already depend on guava and apache-commons, I don't need a third collections library, especially if it has four times (!) the size of the others.
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 tracing MapDB's dependency declaration and locating where Eclipse Collections is used. Determine whether those usages can be replaced without changing supported behavior, then verify that the dependency is no longer included and run the project's existing test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100