this fix of my problem was finally quite simple: i just had to double the backslashes to escape them [1], and then it works, and the generated slingstart.txt contains the same string as before.
what is still strange that on my system (windows 10 machine with java 8) it worked without proper escaping, whereas it failed on Jenkins and on julians machine. stefan [1] https://github.com/apache/sling/blob/trunk/contrib/extensions/contextaware-config/integration-tests/src/main/provisioning/sling.txt#L26 >-----Original Message----- >From: Konrad Windszus [mailto:[email protected]] >Sent: Monday, November 28, 2016 1:06 PM >To: [email protected] >Subject: Re: integration test fail due to LoginAdminWhitelist > >One last addendum: >Since quoted-string in RFC 2616 has some known bugs >(http://stackoverflow.com/questions/7886782/what-is-the-exact-syntax-and- >semantics-of-a-quoted-string-in-the-http1-1-rfc2616) we should only refer >to https://tools.ietf.org/html/rfc7230#section-3.2.6 instead (in the >documentation). > >> 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 >> >
