[JCRVLT-30] Allow package definition to specify recursive install behavior

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1
• Assignee: Tobias Bocanegra
• Reporter: Tobias Bocanegra
• Created: 12/Feb/14 19:32
• Updated: 08/Nov/17 05:31
• Resolved: 18/Feb/14 06:20

Description

Currently it's only possible to control the recursive installation of sub-packages via org.apache.jackrabbit.vault.fs.io.ImportOptions#isNonRecursive().

When dealing with more complex package installation setups, it can be useful to define the recursive behavior in the parent-package directly.

suggest to add a new definition property: subPackageHandling which takes a comma separated list of instructions.

subPackageHandling := instruction { "," instruction };
instruction := packageIdFilter { ";" option }
packageIdFilter := packageNameFilter | groupNameFilter ":" packageNameFilter;
groupNameFilter := "*" | groupName;
packageNameFilter := "*" | packageName;
option := "install" | "extract" | "add" | "ignore";

The default would be:

subPackageHandling = *;install

An example to exclude a subpackage from being installed would be:

subPackageHandling = *;install,somegroup:mypackage;ignore

¹ Note: The difference between install and extract is the snapshot behavior. extract does not create snapshots, install does.

Issue Links

• relates to: JCRVLT-200 Vault should support suppressSnapshots property