What problem does Peaberry for Guice solve?

I understand the problem that OSGI solved thanks to this question....

What does OSGi solve?

And I am already convinved that Guice is amazing so I'm curious what this OSGI integration for Guice known as "peaberry" 开发者_高级运维is supposed to do, it seems to be popping up everywhere, even in Maven 3 presentations.

http://code.google.com/p/peaberry/

It basically allows you to provide and consume OSGi services by binding this into your Guice modules. You could use plain Guice without Peaberry inside OSGi, but it's much easier to use Peaberry for this.

I myself prefer to use Peaberry with it's activation extensions so that I do not need any BundleActivator code in my bundles. This is very similar to be using Spring Dynamic Modules, except that it's all java and typesafe.

It extends Guice to allow injection of OSGi services.