Author: limpbizkit
Date: Sat Nov  1 22:12:39 2008
New Revision: 651

Modified:
    trunk/guice.iml

Log:
Hopefully the last of the big exceptions refactorings. I went through all  
of the places we're adding context to our Errors object and made sure we're  
never doubling-up -- specifing the same injection point or key multiple  
times.

The new errors have nice 'at' lines for parameters, fields and linked  
bindings. Hopefully this makes it easier to follow the stacktraces.  
Additional context (such as the binding's origin in a module) could be  
added later if desired. Currently we have module-specific sources in  
CreationExceptions, and plain old binding sources elsewhere. The end result  
is messages that can look like this:

com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, java.lang.UnsupportedOperationException
   at  
com.google.inject.ProvisionExceptionTest$RealD.<init>(ProvisionExceptionTest.java:284)
   at binding for  
com.google.inject.ProvisionExceptionTest$RealD.class(ProvisionExceptionTest.java:284)
   at binding for  
com.google.inject.ProvisionExceptionTest$D.class(ProvisionExceptionTest.java:1)

1 error

Modified: trunk/guice.iml
==============================================================================
--- trunk/guice.iml     (original)
+++ trunk/guice.iml     Sat Nov  1 22:12:39 2008
@@ -79,6 +79,7 @@
        </library>
      </orderEntry>
      <orderEntry type="library" exported="" name="collect" level="project"  
/>
+    <orderEntry type="module" module-name="multibindings" />
      <orderEntryProperties />
    </component>
  </module>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to