[
https://issues.apache.org/jira/browse/JCRVLT-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608567#comment-15608567
]
Tobias Bocanegra commented on JCRVLT-111:
-----------------------------------------
basically create a test package that contains the new content and put it here:
https://github.com/apache/jackrabbit-filevault/tree/trunk/vault-core/src/test/resources/org/apache/jackrabbit/vault/packaging/integration/testpackages
and then add a test that installs the package, and maybe checks if the imported
content is correct here:
https://github.com/apache/jackrabbit-filevault/tree/trunk/vault-core/src/test/java/org/apache/jackrabbit/vault/packaging/integration
> Add support for o.a.j.api.security.authorization.PrincipalSetPolicy
> -------------------------------------------------------------------
>
> Key: JCRVLT-111
> URL: https://issues.apache.org/jira/browse/JCRVLT-111
> Project: Jackrabbit FileVault
> Issue Type: New Feature
> Reporter: angela
> Assignee: Tobias Bocanegra
> Fix For: 3.1.30
>
> Attachments: JCRVLT-111.patch
>
>
> jackrabbit API has been extended by an additional type of access control
> policy, which isn't an ACL. fvault should be adjusted to be able to properly
> import that type of access control policy.
> as discussed: ac-handling {{MERGE}} and {{MERGE_PRESERVE}} should be
> implemented the same way and just add extra principal names that are not yet
> present in the set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
