[
https://issues.apache.org/jira/browse/SLING-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684948#comment-16684948
]
Carsten Ziegeler commented on SLING-8100:
-----------------------------------------
Yes, I agree - it doesn't make sense for the launcher to check the complete
flag. It's more a marker for the user of the feature
> Allow a feature to be declared as "complete"
> --------------------------------------------
>
> Key: SLING-8100
> URL: https://issues.apache.org/jira/browse/SLING-8100
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Blocker
> Fix For: slingfeature-maven-plugin 1.0.0, Feature Model 0.2.2,
> Feature Model IO 0.2.2
>
>
> This is collected from a thread on the mailing list:
> - a complete feature is self-contained, therefore all requirements must be
> satisfied
> - a non-complete feature may not be launched, so don't try to do that
> - for launching, a complete feature can be used together with both, non
> complete and complete features; it must also be possible to use a set of non
> complete features for launching, together they might form a complete feature.
> Or in other words, the launcher does not care about the complete flag
> - for validation we could add that framework launch properties can only be
> set for a complete feature
> - if features are assembled, the resulting feature is only marked as complete
> if all features used to assemble the feature are complete
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
