You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (Jira)" <ji...@apache.org> on 2022/03/14 10:27:00 UTC
[jira] [Commented] (SLING-11203) Content Loader: Introduce requireImportProvider directive
[ https://issues.apache.org/jira/browse/SLING-11203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506136#comment-17506136 ]
Stefan Seifert commented on SLING-11203:
----------------------------------------
PR from [~enorman]: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/13
> Content Loader: Introduce requireImportProvider directive
> ---------------------------------------------------------
>
> Key: SLING-11203
> URL: https://issues.apache.org/jira/browse/SLING-11203
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Stefan Seifert
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> in context of SLING-11189 [~enorman] proposed the introduction of a {{requireImportProvider}} directive which allows bundles to declare on which import provider implementations they actually depend. with this, it can be ensured a bundle's content is not imported in an inconsistent state when one of the required providers is not (yet) available.
> for backward compatibility this paired with a configurable list of default import providers which is used for bundles which do not declare their own list of via {{requireImportProvider}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)