Willem, as I mentioned on the mailing list. This doesn't actually require a release of camel to fix.
Rather than have people wait for Camel 2.9.0 this can just be patched in guiceyfruit.
Because of the nature of maven's dependency system, this will allow us to exclude the offending version of guiceyfruit and use the guice 3.0 compatible version of it.
Unless the plan is to get rid of guiceyfruit?
I guess that makes sense as the project seems pretty 'dead'. There has been patches for this for a while now and no one has bothered to review them.
Which seems to have caused several projects to fork from it.