Felix Meschberger wrote:
Hi,
On 23.03.2010 15:05, Valentin Valchev (JIRA) wrote:
BTW. Isn't it better to make OBR & SCR a separate plugins.
OBR is not into OSGi core spec, and SCR is IMHO rarely used. The benefits of
that step will be:
1. This will solve the resolve problem we have now
2. OBR activator might track OBR service and register the plugin only when it
is available
3. SCR might be available only if at least one component is installed
A similar approach is used by UPnP Plugin. It will not be visible in console,
unless at least one UPnP Device is available.
This prevents the user from being confused by opening as example "Components" page, that
says "No components".
I am not against this proposal at all, in fact it makes some sense (and
the console bundle itself a bit smaller ;-) and lives by the OSGi ideas).
My question is: Do we want to do this for the Web Console 3.0 release
already ?
One advantage would be to be able to delay the OBR plugin release until
the bundlerepository and utils projects have settled. The disadvantage
of this is, that people upgrading from previous versions of the Web
Console would end without (released) support for OBR.
WDYT ?
IT depends on how much longer people have to wait before an OBR plugin
is available for Web Console 3.0. If it's a matter of weeks, then this
makes sense. If not, then go with earlier plan.
Thanks,
Sahoo
Regards
Felix
