On Sat, Oct 11, 2008 at 5:11 AM, Gili Tzabari <[EMAIL PROTECTED]> wrote: > I don't think you should worry about your users not being used to > external dependencies.
I do NOT want to worry about that, no. Guice is standalone, as it should be. The only option here, IMO, is possibly the idea James Strachan had: having two different jars - one using external libs, and one "jarjar'ed" having "internal libs". This actually seems like a very good tradeoff - if size matters, and you are using these libs more than once, then going through the hassle of resolving jar-hell might be worth it, while if size isn't that big a deal, then just let the different tools have their dependencies internalized. Also, I thought that jarjar thing stripped the libs as bare as possible, only keeping the direct dependent classes, and their deps again. Thus, if Guice is the only lib using such libs, the "total" jar-version will be smaller than the sum of separates. Endre --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" 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?hl=en -~----------~----~----~----~------~----~------~--~---
