[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-update-dev] Why are we not able to disable features that have been included in other features?
|
The update manager currently does not support a notion of "optional
children". This is a recognized requirement, but will not be supported in
2.0. So currently the operations are enabled only on the parent and apply
to the full feature tree.
So the nesting support really cannot be used to package optional features,
and then have the update manager selectively enable/ disable them. Good
enhancement for the next development cycle ...
Pat
McCarthy/Raleigh/IBM@IBMUS To: platform-update-dev@xxxxxxxxxxx
Sent by: cc:
platform-update-dev-admin@e Subject: [platform-update-dev] Why are we not able to disable
clipse.org features that have been included in other features?
06/12/2002 03:11 PM
Please respond to
platform-update-dev
Trying to make sure we have the right approach to our feature definition
and management strategy.
In current builds the disable button is only available on a root
feature.
If we wanted to allow for selective enablement of features, they would
all have to be root features.
What is the reason for this design decision?
Pat Mc.
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev
