[jira] [Updated] (SLING-10334) PrivilegesHandler: regexp never matches privileges definitions from content packages

["Angela Schreiber (Jira)" <ji...@apache.org>]

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

Angela Schreiber updated SLING-10334:
-------------------------------------
    Summary: PrivilegesHandler: regexp never matches privileges definitions from content packages  (was: PrivilegesHandler constructor: regexp never matches privileges definitions from content packages)

> PrivilegesHandler: regexp never matches privileges definitions from content packages
> ------------------------------------------------------------------------------------
>
>                 Key: SLING-10334
>                 URL: https://issues.apache.org/jira/browse/SLING-10334
>             Project: Sling
>          Issue Type: Bug
>          Components: Content-Package to Feature Model Converter
>            Reporter: Angela Schreiber
>            Assignee: Angela Schreiber
>            Priority: Critical
>             Fix For: Content-Package to Feature Model Converter 1.0.26
>
>
> [~kpauls], as discussed the {{PrivilegesHandler}} will never match a _privileges.xml_ file contained in the META_INF folder of a content package. i did an initial test with a AEM specific content package and changing the regexp as follows seems to do the trick:
> instead of 
> {code}
> "META-INF/vault/privileges\\.xml"
> {code}
> the path-pattern should be
> {code}
> "/META-INF/vault/privileges\\.xml"
> {code}
> this will lead to {{PrivilegesHandlerTest.matches}} to fail but that one is anyway a bit odd.... the next test {{parsePrivileges}} uses a path {{String path = "/META-INF/vault/privileges.xml";}}, which wouldn't match but since {{PrivilegesHandler.handle}} is directly called it wasn't noticed.
> will try to come up with a reasonable test package that illustrates the issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)