Thank you Williem! It should be worth mentioning that this fix could be as simple as creating a non-internals depending release of guiceyfruit. That would allow people to use it in current versions of camel with no other changes as well as later versions of camel to use.
On Mon, Jul 11, 2011 at 3:41 AM, Willem Jiang <[email protected]>wrote: > Hi, > > I just created a JIRA[1] to trace this issue. > > [1]https://issues.apache.org/**jira/browse/CAMEL-4209<https://issues.apache.org/jira/browse/CAMEL-4209> > > > On 7/9/11 12:42 AM, Tim wrote: > >> camel guice is using guice 2.0 >> Which wouldn't be so bad except that it uses things from the guice >> internal >> packages. >> This makes it impossible to use it alongside guice 3.0 >> >> I can't see any new version of guice 3. >> I realize this isn't a 'camel' problem but the committers of guiceyfruit >> are >> also camel committers. >> >> Has anyone found a way to get camel-guice working with guice 3 otherwise? >> >> Thanks >> >> > > -- > Willem > ------------------------------**---- > FuseSource > Web: http://www.fusesource.com > Blog: > http://willemjiang.blogspot.**com<http://willemjiang.blogspot.com>(English) > http://jnn.javaeye.com (Chinese) > Twitter: willemjiang > Weibo: willemjiang >
