Hi, I just figured out that non-applicable or incorrect repoinit statements do not consistently lead to an exception (and therefore prevent the repository from starting). E.g. since https://issues.apache.org/jira/browse/SLING-9449 <https://issues.apache.org/jira/browse/SLING-9449> a failure of setting principal ACLs just leads to a WARN. I would appreciate a consistent error handling across all statements and also I think that throwing an exception is useful as it makes debugging a lot easier.
Continuing with non-evaluated repoinit statements is dangerous as then the repository does not have the desired state... WDYT? Thanks, Konrad
