[
https://issues.apache.org/jira/browse/JCRVLT-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605949#comment-16605949
]
Dominik Süß commented on JCRVLT-319:
------------------------------------
[~tripod] - a proposal is available under
https://github.com/apache/jackrabbit-filevault/pull/36 - test coverage for
scenarios will be added later today. Anyhow if I can't make it before you have
a look please crosscheck the API addition and general idea of the
implementation change - this basically just prevents the effective packagetasks
for those to be generated (consumer claims to take care of those).
Additionally, I changed that the packagetask type is promoted down to avoid
install tasks to pop up through an extract task dependency.
> Allow building of stacked ExecutionPlans
> ----------------------------------------
>
> Key: JCRVLT-319
> URL: https://issues.apache.org/jira/browse/JCRVLT-319
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Reporter: Dominik Süß
> Assignee: Dominik Süß
> Priority: Major
>
> The implementation of ExecutionPlanBuilder currently does not provide an
> option to "pre-satisfy" dependencies when building but always checks for the
> install state.
> This comes with the following downsides:
> * it is not possible to prebuild stacking execution plans that would be
> satisfied/valid when executed in sequence - as soon as the validation is
> being performed the second plan automatically spawns install tasks for the
> packages missing
> * The tasks for missing dependencies are automatically created with
> PackageTask.Type.INSTALL even if all other tasks are EXTRACT tasks.
> This improvement is about adding some kind of DependencyValidationHandler
> which allows controlling how to handle a "missing" dependency (default
> behavior right now is to check if already installed and add an install task
> if missing)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
