Split the jars into smaller pieces

[gissuebot]

Original issue created by davide.cavestro on 2013-11-28 at 11:14 AM

---

I'd like to introduce Guava into a client application distributed through Java Web Start, but in this scenario it's not acceptable to increase the download with additional 2mb for the guava jar, and this time I'd like to use "only" guava collections features.
AFAIK there's only a way to get a distribution for a limited set of guava features: regenerating the jar with some tools (i.e. with CodePro, as yuou explained at https://code.google.com/p/guava-libraries/wiki/UsingProGuardWithGuava )
But this kind of approach is considered burdensome and risky for maintenance, hence some people reject guava (or at least this factor so far limited its adoption on my projects).

So wouldn't it be good if you split the library into smaller pieces with appropriate deps and publish them to maven?

[gissuebot]

Original comment posted by ogregoire on 2013-11-28 at 12:57 PM

---

How is it burdensome if you integrate Proguard in whatever tool you use to build your application? I understand you use Maven. There are plugins to do that, as explained in this StackOverflow: http://stackoverflow.com/questions/10929236/proguard-maven-with-java-7

[gissuebot]

Original comment posted by kak@google.com on 2013-11-28 at 01:14 PM

---

(No comment entered for this change.)

---

Status: Duplicate
Merged Into: #605

[gissuebot]

Original comment posted by davide.cavestro on 2013-11-28 at 01:20 PM

---

I use Gradle, in the previous post I mentioned Maven as a shortcut for public Maven repositories. Using ProGuard is surely feasible (some time ago I've integrated other tools like yguard) but the problem is that by splitting 3rd party contents using custom rules you have the new burden of maintaining them as soon as you want to upgrade the deps.