[
https://issues.apache.org/jira/browse/SLING-12469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-12469.
-------------------------------------
Resolution: Fixed
> Index definitions are not extracted when individual definitions are defined
> in the filter.xml as roots
> ------------------------------------------------------------------------------------------------------
>
> Key: SLING-12469
> URL: https://issues.apache.org/jira/browse/SLING-12469
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.3.8
>
>
> Assuming that we have a content package with index definitions stored as
> single files
> {noformat}
> .
> ├── jcr_root
> │ └── _oak_index
> │ ├── .content.xml
> │ └── foo.xml
> └── META-INF
> └── vault
> └── filter.xml
> {noformat}
> WIth the filter listing the individual index definitions
> {noformat}
> <?xml version="1.0" encoding="UTF-8" ?>
> <workspaceFilter version="1.0">
> <filter root="/oak:index/foo" />
> </workspaceFilter>
> {noformat}
> Then the index definitions will not be extracted properly. The root cause is
> that the repository path for the filter is inferred as {{/oak:index/foo.xml}}
> - file extension included. This will cause it to not match the filters.
> Looks like we need to better set the repository paths by following the
> aggregation logic better. IIUC, according to
> https://jackrabbit.apache.org/filevault/config.html#aggregates , foo.xml is
> handled by a FullCoverageAggregator and should have the extension removed.
> Care must be taken to not apply the same logic to the entries handled by
> FileAggregator, whose extension must be kept. This is the case for Tika
> configurations, for instance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
