On 9 Dec 2013, at 7:39, Thomas Matthijs wrote:
1) Do you want Guice to embed Guava or to make it a real dependency?
I would prefer both like cglib does for example, have a main 'guice'
artifact with a dep, and one with guava shaded as 'guice-nodeps' for
example.
Dependency conflicts with these base libraries everyone uses can be a
lot
of work without an escape hatch like this, but i'd encourage people to
use
the one with the dep.
That's not too crazy to set up, though since we have two build systems -
ant AND maven, it's a bit fraught to make both happen. But this is
certainly not infeasible.
I would prefer to have guava a separate dependency, but I'm biased (I'm
on the same team that releases Guava, and I have done a lot of the guava
build stuff), and I think Sam wanted opinions from the community. ;)
2) Is it OK for Guice to bump it's minimum requirements up to Java6?
Definitely, have to move forward, people that require java 5 can keep
using
the current version of guice.
Again, I'm biased (I'm also one of the primary dagger developers) but I
definitely think Guice needs to be un-constrained by this android
limitation). So my vote is clearly Java6.
c.
Christian Gruber :: Google, Inc. :: Java Core Libraries :: Dependency
Injection
email: [email protected] :::: mobile: +1 (646) 807-9839
--
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice.
For more options, visit https://groups.google.com/groups/opt_out.
