http://code.google.com/p/google-guice/wiki/Guice30

Any news on this front?

This new Guice now requires the javax.inject jar, which originates from
http://code.google.com/p/atinject/ and uses the Apache 2.0 license.


[INFO] +- com.google.inject:guice:jar:3.0:compile
[INFO] |  +- javax.inject:javax.inject:jar:1:compile
[INFO] |  \- aopalliance:aopalliance:jar:1.0:compile


On Sun, Mar 13, 2011 at 7:52 PM, Han Nguyen <[email protected]> wrote:

> Hi Henry,
> We aren't sure and that is why we need a little time to ensure we can
> maintain consistency with our current JSR 330 implementation that ships in
> our Java certified products today
>
>
>
> From:   Henry Saputra <[email protected]>
> To:     [email protected]
> Date:   03/11/2011 04:49 PM
> Subject:        Re: guice 3.0-rc3
>
>
>
> Hi Han,
>
> Could you explain more on how would this impact interoperability with
> your internal JSR330 implementation?
>
> - Henry
>
> On Fri, Mar 11, 2011 at 1:40 PM, Han Nguyen <[email protected]> wrote:
> > -1... with recommendation that we put this vote on hold and revisit in
> > about 2 weeks to allow our team to validate interoperability and ensure
> > that we can maintain consistency with our internal current jsr 330
> > implementation that we ship with products today.
> >
> >
> >
> >
> > From:   Paul Lindner <[email protected]>
> > To:     [email protected]
> > Date:   03/10/2011 11:49 AM
> > Subject:        guice 3.0-rc3
> >
> >
> >
> > Guice 3.0 is very close to release.  To help us prepare for this I would
> > propose that we upgrade to this version in trunk.  There are a number of
> > reasons why 3.0 is preferred including better OSGi support and jsr330
> > support that should make integrating easier.  More details are here:
> >
> > http://code.google.com/p/google-guice/wiki/Guice30
> >
> > If no one objects I'll commit the pom changes late this week.
> >
> > --
> > Paul Lindner -- [email protected] -- linkedin.com/in/plindner
> >
> >
>
>
>
> --
> Thanks,
> Henry
>
>


-- 
Paul Lindner -- [email protected] -- linkedin.com/in/plindner

Reply via email to