On Jan 27, 9:00 am, nimbus <[email protected]> wrote: > Understand that adding the option may not be the most desirable course > of action at this stage. Also, saw the recent message from Jesse (in > the thread on the Guice 2 release schedule) that the API should now be > considered as frozen,. > > Obviously, my preference would be to remove the change in order to > preserve contract compatibility with Guice 1. Also note that the > request was originally closed with status "WontFix" for this reason, > and was only later re-opened and implemented. > > So, is there any possibility of removing the change now ?
If we were to permit this, it would probably take the form of a Java system property, like we did to allow 'null' before we had the @Nullable annotation. That approach is quite clumsy because it means we have to test everything twice, once with the flag and once without it. Sometimes you forget to set the property, or don't set it soon enough in the execution of the program, and things don't work the way they should. So I prefer to avoid system properties when I can. It seems like using a patched .jar would probably be easier. You eliminate the runtime configuration hassle of setting the property, and it's much more obvious from the classpath that you're not using the standard Guice behaviour. If you'd like, I provide the patch and instructions for using it to build a .jar. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
