I had a similar exception when mixing extensions from Guice 3 with Guice 4. In my project, I use Guice 4.0-beta4, but a few dependencies (namely Jukito and Closure Templates) use Guice 3.0 and bring guice-multibinding and guice-assistedinject in their version 3.0. Because the jarjar-ing treatment changed between versions, they don't play well together, so I need to declare those transitive dependencies with version 4.0-beta4 in my POM's dependencyManagement.
Side not: it would be easier if there was a "BOM", i.e. a pom.xml that lists all the possible dependencies (Guice core and extensions) with the same version in a <dependencyManagement> section, so it can be used with <scope>import</scope> to make sure you don't have version mismatches when deps transitively bring Guice extensions. That pom.xml could be guice-parent for example, or a new com.google.inject:guice-bom. See http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies On Wednesday, May 21, 2014 9:08:50 AM UTC+2, Stuart McCulloch wrote: > > > On 21 May 2014 08:00, "Christian Kütbach" <[email protected] <javascript:>> > wrote: > > > > We have the same Problem (running inside IBM Notes). > > > > Are there any solutions found, yet? > > The original poster didn't reply with details of how to recreate the > error, exactly what versions were involved, etc. > > If you can tell us exactly how to recreate this exception then it should > be straightforward to track down and fix. > > -- > Cheers, Stuart > > > > > > > Regards, > > Christian Kütbach > -- You received this message because you are subscribed to the Google Groups "google-guice" 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. For more options, visit https://groups.google.com/d/optout.
