To figure out how the escaping exactly works, you can leverage the JCR Installer write back feature (which gives out .config files in the repository)
> On 28 Nov 2016, at 12:54, Konrad Windszus <[email protected]> wrote: > > Currently we have more or less the same documentation at > https://sling.apache.org/documentation/bundles/configuration-installer-factory.html#configuration-files-config > and > https://sling.apache.org/documentation/development/slingstart.html#default-configuration-format. > I would be in favor of getting rid of the description in the latter page and > just link to the former. > In the former page the escaping rules should be further clarified. > Konrad > >> On 28 Nov 2016, at 12:45, Stefan Seifert <[email protected]> wrote: >> >> >>> Your current configuration looks like this: >>> whitelist.bundles.regexp="^org\.apache\.sling\.junit(\..*)?$" >>> >>> Inside target/slingstart.txt this becomes: >>> whitelist.bundles.regexp="^org.apache.sling.junit(..*)?$" >>> >>> Note: all slashes have disappeared. >> >> this is strange, yes. >> the same escaping problem happens on my local machine - but there the >> integration test passes. >> you could reproduce the problem on your machine? >> >> as a workaround i will simplify the regex and remove the backslashes. >> >> i think we have currently no precise documentation of the sling provisioning >> file format esp. regarding escaping rules. on [1] only some details of the >> embedded osgi configuration format are documented. >> >> stefan >> >> [1] https://sling.apache.org/documentation/development/slingstart.html >> >
