Woops - quick correction. @com.google.inject.Inject does support injection of final fields, and Guice supports this feature still... but @javax.inject.Inject is specified to not support this feature.
I mentioned it in the announcement because we have removed some "final"s in annotated guice extension code, in anticipation of migrating as much as possible to use @javax.inject.Inject. But there is no breaking change in this release. That was my mis-remembering. Apologies. That said, it is not recommended practice, since it is not compatible with the JSR-330 spec, and uses reflection cheats that are not guaranteed to work in the context of some SecurityManagers or signed/sealed jars. So - warning delivered, carry on. :) Christian. On Thursday, 20 March 2014 20:59:37 UTC-7, Christian Gruber wrote: > > > - Stronger support for and adherence to JSR-330 > - @Inject on final fields prohibited (matches javax.inject.Inject > semantic) > > -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice. For more options, visit https://groups.google.com/d/optout.
