Thanks for the input.
Although this is easy to determine for new/modified index definitions, this is
impossible to tell for paths below /oak:index which are just getting removed
(i.e. are just listed in the filter). I guess for the latter we have to assume
the worst, case i.e. that an existing
Hi Konrad,
As written in JCRVLT-345, I don't think that we should add a lot of
validation features into the filevault-package-m-p, as validation can
happen more often during the lifetime of a package (e.g. before deployment
if developer and deployer/operation are not identical). I would move all
Hi Konrad,
rep:policy should for sure not cause issues - but ACLs are orthogonal to
the index definitions. IIrc stuff like excludePath etc may be defined
bellow and changes in there should fail.
Do option D would be to just exclude the ACL handling which anyhow is
handled quite specifically
Hi,
the filevault-package-maven-plugin validates if a package contains a new index
definition. This behaviour can be disabled via the "allowIndexDefinitions"
parameter
(https://jackrabbit.apache.org/filevault-package-maven-plugin/generate-metadata-mojo.html#allowIndexDefinitions)
. There was
