It already happens if you're using struts 2, every time you need to choose @Inject betwen guice or xwork. anyways, nobody had complained before ;)
On Tue, Sep 8, 2009 at 11:00 PM, Robbie Vanbrabant < [email protected]> wrote: > Maybe the next Guice release could have two guice.jar's, one with the > legacy annotations and one without :) > What's the problem with @Named? > > Cheers > Robbie > > > On Tue, Sep 8, 2009 at 4:22 AM, [email protected] <[email protected]>wrote: > >> >> I've implemented support for JSR-330 to Guice. This JSR standardizes >> annotations like @Inject and the Provider interfaces for Java >> platforms. It doesn't yet specify how applications are configured, so >> it has no analog to Guice's modules. >> >> This new feature may cause pain for IDE users. Since there's now two >> @Inject annotations, IntelliJ etc. will prompt you when it needs an >> import. Either one will work, but the new dialogs will be quite >> annoying! Even worse, the two @Named annotations aren't (yet) >> equivalent. So if you apply the wrong annotation, you'll get a >> configuration error. I'm thinking about ways to address this. >> >> This work is ongoing. I recommend continuing to use the old >> com.google.inject annotations until the dust settles. >> http://code.google.com/p/google-guice/wiki/JSR330 >> >> 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 -~----------~----~----~----~------~----~------~--~---
