You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2022/04/04 20:28:00 UTC

[jira] [Resolved] (SLING-11203) Content Loader: Introduce requireImportProvider directive

     [ https://issues.apache.org/jira/browse/SLING-11203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Norman resolved SLING-11203.
---------------------------------
    Resolution: Fixed

Merged PR at [{{768e44c}}|https://github.com/apache/sling-org-apache-sling-jcr-contentloader/commit/768e44ce99a223f886a21a4bd3000cf2cc2b26e6]

> 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
>            Assignee: Eric Norman
>            Priority: Major
>             Fix For: JCR ContentLoader 2.5.4
>
>          Time Spent: 1h 50m
>  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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)