-1 to new external dependencies. I'd rather Guice be free to innovate rather than tie itself to a particular version of an external library. Not to mention the added headaches when my app already uses one version of an external library but now Guice thinks I should have a different version of the library, and they have conflicts.
Furthermore, Guice works well on Android now. Adding external library dependencies may make this more complicated. On Thu, Jun 10, 2010 at 11:11 AM, Christian Edward Gruber < [email protected]> wrote: > +1. > > On Jun 10, 2010, at 7:04 AM, Johannes Schneider wrote: > > On 06/03/2010 04:31 PM, [email protected] wrote: > > Moving these classes is a fine idea, but it will cause pain for any > > developer who has mistakenly imported Guice's ImmutableSet (etc.) > > rather than that from Guava. > > > Maybe it is a good idea to remove that "interal" classes completly and > instead create a dependency to Guava? > > In nearly every project, I have many duplicates... > > > -- > 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]<google-guice-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-guice-dev?hl=en. > -- Eric M. Burke http://www.linkedin.com/in/ericburke 314-494-3185 (mobile) 636-294-0191 (home) -- 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.
