Interesting. How about instead of killing Plugins, we keep them?
One issue that I have with the current set-up of framework is proper set-up of launcher-bundles in test.config.properties as well as other set of properties.
I would be a nice extension to have a Plugin, call it a DefaultKernelSetupPlugin that can be simply included by client to get a correctly ordered list of kernel bundles. Attributes can be something like a prefix to use to resolve location of bundles and potentially others.
Another plugin could be targeted at web container set-up. With additional properties specific to web container, i.e. port number etc.
Another plugin that I am thinking about - can be used to deploy extra bundles with help of ArtifactDeployer vs. having to provide a "transitively complete" enclosure of bundles to deploy (as BundleDependencies require now). Maybe with a new annotation like UserRegionBundleDependencies or a reuse of BundleDependencies.
Thoughts?
Regards,
Dmitry
On Tue, Dec 21, 2010 at 4:45 AM, Glyn Normington
<gnormington@xxxxxxxxxx> wrote:
On 20 Dec 2010, at 20:08, Dmitry Sklyut wrote:
> While we are on the subject of test framework - what was the idea behind @Plugins annotation and Plugin interface?
I don't think those are used, but the original idea was to support plugins of the test framework so that standard sets of bundles could be installed. The code can probably be deleted.
Regards,
Glyn
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
