I would definitely remove the current h. injector implementation for
2.0.
Brian

On Sep 9, 11:37 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I'd promised Guice 2.0 for 'summer 2008',
> and here we are, with ten days left before
> fall 2008. Time is up, but the promised
> features are still incomplete!
>
> What we're behind on...
>
> Hierarchical Injectors. These need some
> serious love. We need this internally at
> Google, and I really want to make sure this
> is done right.
>
> Struts2, Servlets, OSGi. I've got to go
> through some patches from Stuart and
> Dhanji to get these things working nicely.
>
> Circular Dependencies. I want to rewrite
> the injection loop so we can do circular
> dependencies cleanly without proxies.
>
> The Plan...
>
> The code has come a long, long way since
> Guice 1.0 and I'd quite like it if we could
> get something of release quality out for
> folks to start using. I'm thinking of polishing
> up the current code (Javadocs, etc.) and
> calling it 'Guice 2.0'.
>
> Even without the new features it's still a
> huge update, and worthy of your time to
> upgrade. (hello, @Provides)
>
> Once that's available, I'll keep working, and
> get Guice 2.1 out during 'fall 2008'. This
> should contain all of the slipped features.
>
> How you can help...
>
> Run your application's test suite using today's
> snapshot, and report any regressions:
>  http://code.google.com/p/google-guice/downloads/detail?name=guice-sna...
>
> Try out the new APIs, and reply with your
> comments. Recent Javadoc is here:
>  http://google-guice.googlecode.com/svn/trunk/latest-javadoc/index.html
>
> Thanks,
> 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