Currently you can inject Eclipse extensions into JSR330 applications by registering the appropriate peaberry bindings in a custom Guice binding module. We should try to make this more automatic by including results from the Eclipse extension registry (if available) when looking up bean implementations via the BeanLocator.
Comment 2397529
Date: 2014-05-06 10:18:09 -0400
From: Stuart McCulloch <mcculls@gmail.com>
This issue was created automatically with bugzilla2github
Bugzilla Bug 386434
Date: 2012-08-01 18:40:10 -0400 From: Stuart McCulloch <mcculls@gmail.com> To: Project Inbox <sisu-inbox@eclipse.org> CC: gm.romanato@gmail.com
Depends on: #386430 See also: https://issues.sonatype.org/browse/SISU-7 Last updated: 2015-02-11 12:09:56 -0500
Comment 2144111
Date: 2012-08-01 18:40:10 -0400 From: Stuart McCulloch <mcculls@gmail.com>
Migrated from https://issues.sonatype.org/browse/SISU-7
Currently you can inject Eclipse extensions into JSR330 applications by registering the appropriate peaberry bindings in a custom Guice binding module. We should try to make this more automatic by including results from the Eclipse extension registry (if available) when looking up bean implementations via the BeanLocator.
Comment 2397529
Date: 2014-05-06 10:18:09 -0400 From: Stuart McCulloch <mcculls@gmail.com>
Logged https://dev.eclipse.org/ipzilla/show_bug.cgi?id=8265 to track potential re-use of IP from Peaberry (which I also created) in implementing this feature.
Comment 2517466
Date: 2015-02-11 12:09:56 -0500 From: Stuart McCulloch <mcculls@gmail.com>
Moving out of 0.3.0 scope, current focus is on service publisher first then extensions.