Status: New Owner: ---- New issue 289 by gili.tzabari: Provide JarJar-less builds in official releases http://code.google.com/p/google-guice/issues/detail?id=289
There has been a long history of problems using JarJar-processed files. I suggest you offer two kinds JAR files in official builds: module-all.jar includes dependencies module.jar excludes dependencies This is a well established paradigm used by many other open-source projects. In fact, I would go a step further and suggest that you simply offer guice-all.jar for JarJar users (includes all plugins) and separate JAR files for non-JarJar users. This should be extremely easy to implement and users would actually see a size decrease relative to the current builds (which uses JarJar separately per plugin which is expensive). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en -~----------~----~----~----~------~----~------~--~---
