I mentioned a few times that Jersey (JAX-RS reference implementation)
would like to incorporate a Guice plugin into their upcoming release.
The only way that will happen is if we have a formal Guice release to
work against (as opposed to working off trunk). There have been
sufficient SPI changes since Guice 1.0 that I wouldn't consider
integrating against it.
I would like to see a feature-frozen Guice 2.0 that I could code
against. Guice 2.1 could then come around with bug fixes and performance
improvements but the API would remain the same so my plugin would remain
relevant.
In your opinion, what remains to be done before Guice 2.0 can be
released? What timeline is realistic?
PS: Please note that JAX-RS relies on a fix for
http://code.google.com/p/google-guice/issues/detail?id=288 so be sure to
nail down any API changes in this department before 2.0
Thank you,
Gili
Dhanji R. Prasanna wrote:
>
>
> On Tue, Jan 27, 2009 at 8:52 AM, Gili <[email protected]
> <mailto:[email protected]>> wrote:
>
>
> What's going on with Guice these days? Has Google tightened the bolts
> on this project because of the economy? We haven't heard any news with
> respect to Guice 2.0 in a long while and I'm getting the feeling that
> Guice integration won't make it into JavaEE 6. SVN logs also fell
>
>
> Java EE 6 integration? I am not aware that there are any plans to
> integrate with Java EE 6 (I am an EG member).
>
> Dhanji.
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
