+1 for #5. There are legit cases for needing different dependency versions in larger projects and having that flexibility is a big plus. Besides, for the default case, a maven or regular zip distributions could automatically point or include the official, tested Guava version for a given Guice version.
-- yuri On Tue, Jul 5, 2011 at 4:15 PM, James Moore <[email protected]> wrote: > Speaking as a Guice + Guava (on Android) user, I'd vote for #5, make > Guava an external dependency. > > 1) Do nothing (and live with the larger jar size where we basically > embed all of Guava) > > I think this is a problem from the Android point of view. What > happens when you're still on Guava r09, and I want r10? (That's the > situation right now, I think, since I'm switching to trunk Guava/r10 + > Guice). That's a lot of extra duplicated code to have installed. > > -- > James Moore > [email protected] > http://jamesmoorecode.blogspot.com/ > > -- > 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. > > -- 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.
