Comment #10 on issue 70 by robbie.vanbrabant: Support any annotation in place of @Inject http://code.google.com/p/google-guice/issues/detail?id=70
I am always very skeptical when people talk to me about "framework portability". I have never seen a company port their code to another framework without touching it, and usually they don't port, they rewrite. So then the question is, should Guice use @Resource instead if @Inject? My answer: when it makes it into SE, _maybe_. So then there's the other issue people are talking about, and what Jesse called the "perceived" problem. Having to import com.google.inject is indeed a perceived problem from a technical perspective, but I understand that this can be a political problem in larger companies. If we decide to tackle this problem I think we should mimic the @Nullable feature and allow any annotation named @Inject. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
