Comment #12 on issue 70 by stolsvik: Support any annotation in place of @Inject http://code.google.com/p/google-guice/issues/detail?id=70
@Robbie: Who is one to decide what others should find a problem? Just because you find it fantastic to include a dependency on any random library, others might not. Letting Guice handle other annotations than its own seems so amazingly obvious and merely an extension of its own point of existence that I don't at all understand why it wasn't included in the first place. .. and definitely not why it isn't in the code now. Reusable code is a good thing. If the code in questions tags its injection-needs with its OWN annotations, it should be possible to state to the injection framework what these annotations are. This instead of making a resource provider. At this point it is even possible to use a _standard_ set of annotations. That Guice should support this is, at least for me, absolutely obvious. -- 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 -~----------~----~----~----~------~----~------~--~---
