By creating a small JAR with the classes listed here: https://github.com/etesla/xtext-guice2-internal/tree/master/src/main/java/com/google/inject/internal
I was able to run Xtext with Guice 3 inside Maven 3.x. These classes don't look generated so maybe I encountered something different than what you are describing. On Oct 23, 2011, at 1:52 PM, Sven Efftinge wrote: > Thanks. Note, that we had to patch the original code. We had to make sure > that generated byte code is not put into a signed package (all our packages > are signed). > Sebastian, could you outline where and how you patched the code, so Jason is > able to apply it to Guice 3 as well? > > On Oct 23, 2011, at 7:43 PM, Jason van Zyl wrote: > >> Ok, I will post my findings regarding running Guice 3 and Xtext. Boils down >> the Xtext using some internal classes in Guice 2 that were relocated in >> Guice 3. >> >> Jason >> >> On 2011-10-23, at 9:31 AM, Sebastian Zarnekow <[email protected]> >> wrote: >> >>> Hi Jason, >>> >> >> >> _______________________________________________ >> xtext-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/xtext-dev > > _______________________________________________ > xtext-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/xtext-dev Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau
_______________________________________________ xtext-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/xtext-dev
