Comment #2 on issue 774 by [email protected]: Modules.override() loses
source information when the current source is skipped
http://code.google.com/p/google-guice/issues/detail?id=774
I was going to cook something up, but I just realised that you can't handle
multiple nested modules that should all be skipped. The inner module
doesn't know that the outer one is skipped too.
Another solution is to delay computing the skipped sources until later.
Element.applyTo() would still call binder.withSource(), but pass it the
whole stack trace instead of just the top element. The binder would go
through the stack trace until it found an element that wasn't skipped.
But that's a huge change for a reasonably corner case. I'm open to other
suggestions.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" 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-dev.
For more options, visit https://groups.google.com/groups/opt_out.
