[
https://issues.apache.org/jira/browse/SLING-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-10140.
---------------------------------
Resolution: Fixed
Fixed at:
[https://github.com/apache/sling-org-apache-sling-bundleresource-impl/commit/54c2d6949c3c0e4714c51d30ef2841af38e52e35]
Also added new unit test to verify the fix.
> Handle defining resources through JSON when the resourceRoot is a file that
> is mapped to a different entry path
> ---------------------------------------------------------------------------------------------------------------
>
> Key: SLING-10140
> URL: https://issues.apache.org/jira/browse/SLING-10140
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: Bundle Resource 2.3.4
>
>
> Handle the special case when the resourceRoot points to a mapped file and
> also has a "propsJSON" directive.
> In this case, the "propsJSON" sibling entry may still exist in the bundle but
> it would not be contained within the mappedPath set since it is not a
> descendant of the resourceRoot. So additional logic is needed to locate the
> "propsJSON" entry for this file.
>
> For example:
> {code:java}
> Sling-Bundle-Resources:
> /products.txt;path:=/resources/products.txt;propsJSON:=json{code}
> For this example, if the /resources/products.txt.json file exists in the
> bundle, it should be loaded and used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
