I would like to be able to limit the source of injected components in Eclipse. For example if software X requires consumers to implement interface A to provide usage specific context, when multiple consumers of software X are present how should each consumer ensure their implementation of A is injected into their instance of software X?
It appeared in limited testing that the first implementation of A injected was then used in subsequent injections of software X for other consumers.
This issue was created automatically with bugzilla2github
Bugzilla Bug 386443
Date: 2012-08-01 18:54:32 -0400 From: Stuart McCulloch <mcculls@gmail.com> To: Project Inbox <sisu-inbox@eclipse.org>
See also: https://issues.sonatype.org/browse/SISU-88 Last updated: 2013-07-16 21:17:03 -0400
Comment 2144121
Date: 2012-08-01 18:54:32 -0400 From: Stuart McCulloch <mcculls@gmail.com>
Migrated from https://issues.sonatype.org/browse/SISU-88
I would like to be able to limit the source of injected components in Eclipse. For example if software X requires consumers to implement interface A to provide usage specific context, when multiple consumers of software X are present how should each consumer ensure their implementation of A is injected into their instance of software X?
It appeared in limited testing that the first implementation of A injected was then used in subsequent injections of software X for other consumers.