Comment #1 on issue 718 by [email protected]: Misplaced annotation check
may be overly strict when dealing with legacy code
http://code.google.com/p/google-guice/issues/detail?id=718
Just for reference, attached is our current hack to turn off strict
misplaced annotation checks for specific isolated legacy applications. A
better approach would be to expose a non-strict setting via some kind of
binder option or perhaps a new stage. Although ideally such applications
would eventually be fixed and no such change would be required.
Attachments:
GUICE_718_20120729.txt 1.8 KB
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" 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-dev?hl=en.
