You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/02/10 12:02:00 UTC

[jira] [Resolved] (SLING-11744) Allow configuration of include and exclude paths for bundles

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

Carsten Ziegeler resolved SLING-11744.
--------------------------------------
    Resolution: Fixed

Added support for include/exclude paths; default include configuration is /libs and /apps.

> Allow configuration of include and exclude paths for bundles
> ------------------------------------------------------------
>
>                 Key: SLING-11744
>                 URL: https://issues.apache.org/jira/browse/SLING-11744
>             Project: Sling
>          Issue Type: Improvement
>          Components: i18n
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: i18n 2.6.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> By default, resource bundles are searched in the whole repository. Allowing to more fine tune the parts in the repository has some benefits:
> - Better control of where bundles can be located and who is able to edit those
> - More effective querying and change tracking as only parts of the repository are searched
> While there is already a configuration named  excluded.paths, that one only covers Observation Event handling - which is not the same as a deny list. It still allows to load bundles from the paths, but just prevents updateds.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)