Hi Ioannis,
I don't understand the usage of an inner feature. Basically, what the
differences between a top level feature and an inner feature ?
If the assumption is that the inner feature life cycle (install,
uninstall, start, stop) is the same as its parent feature, why not
putting directly the bundles into the parent feature ?
I'm not sure that the support of inner features is a good thing.
If we want to still support that, I think that we can add a lifecycle
attribute which can have value like "isolated" (the inner feature is
managed as a top level feature, isolated from its parent feature),
"parent" (the inner feature life cycle match the parent feature).
Regards
JB
On 05/21/2011 08:36 AM, Ioannis Canellos wrote:
A week ago I saw a question in the user list regarding uninstalling inner
features.
Our reply was that when a feature gets uninstalled its inner feature remain
there (which is how things currently work).
Wouldn't be great if we could implement a mechanism that would uninstall
inner features too, as long as their bundles do not contain packages
imported by bundles outside the feature?
An alternative would be to add an attribute on inner features to specify
wether the inner feature will be uninstalled or not.
The reason I am thinking about this is that on really large projects, it
make things cleaner to reuse features as inner features, but its a pain to
uninstall them.
wdyt?
