Jesse,

        I really appreciate your reply and the efforts you have all poured into 
this.

        With respect to the new reference caching code, would it be possible 
for you to commit it to trunk? I would love to test it against my 
Glassfish configuration, where we first saw this problem. If there are 
any remaining Glassfish issues I want to throw it back in their lap as 
soon as possible.

        With respect to the snapshot release, my only concern is whether the 
JarJar issue for AssistedInject was resolved. If you can put out an 
official snapshot build and put out some semi-official announcement that 
the 2.0 API is frozen then I suspect it will go a long way towards 
convincing the JAX-RS lead.

Thank you,
Gili    

[email protected] wrote:
> On Jan 26, 3:25 pm, Gili Tzabari <[email protected]> wrote:
>>         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.
> Dude, you're keeping me honest. Thank you. I'm not at all happy that
> our release is slipping, but it's slipping! We're busy busy, and
> unfortunately it's on non-Guice stuff (my day job is contributing to
> the new hotness billing frontend for AdWords).
> 
>>         In your opinion, what remains to be done before Guice 2.0 can be
>> released? What timeline is realistic?
> Almost nothing. There's a few issues with the servlets code (we need
> to be careful about some static references), and Bob's rewritten our
> reference caching so that it doesn't cause grief for J2EE users when
> it starts its own thread. But we are trying to 'bake' the release by
> running it internal to Google for a couple weeks before we stamp a
> release number on it. Rushing into releases might mean that we'd
> release 2.0, and then an embarassing 2.0.1, etc.
> 
>> PS: Please note that JAX-RS relies on a fix 
>> forhttp://code.google.com/p/google-guice/issues/detail?id=288so be sure to
>> nail down any API changes in this department before 2.0
> The API that's in SVN is the final 2.0 API, I promise. I'll try to get
> something out very soon (a snapshot at minimum) so you have a formal
> binary from we the Google.
> 
> Cheers,
> Jesse
> > 
> 

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to