|Re: Problems with Run Configuration with Selected Features [message #633821 is a reply to message #606873]
||Tue, 19 October 2010 14:12
Registered: October 2010
Again, thank you for the reply.|
I'm still unsure, though, if the resolution mechanics you describe are the most appropriate.
Concretely, our problem is that we use fragments to contain test code for each of our bundles. And we only want those fragments included when we run our unit tests.
There are also a number of other use cases for fragments, e.g. the example from the OSGi spec of providing translation files for different locales, that seems to require control over whether or not a fragment is deployed. Consider an English and a French localization fragment, where you only want one of those.
It makes the way features are interpreted in run configurations a lot less useful, that all of the fragments in the workspace are considered part of the application rather than only those specified in the selected features.
My intuitive understanding of what it would mean to "Launch with: features selected below" is that it should be equivalent to "Launch with: plugin-ins selected below" where the plug-ins selected are exactly those specified by the features.
This interpretation gives complete control over which plug-ins and fragments are used in a run configuration. It would also make the use of features in run configurations coherent with the use of plug-ins/bundles, in that you only get what is specifically selected in the run configuration.
Powered by FUDForum
. Page generated in 0.02074 seconds