jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCRVLT-30) Allow package definition to specify recursive install behavior
Date Tue, 18 Feb 2014 05:44:19 GMT

     [ https://issues.apache.org/jira/browse/JCRVLT-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tobias Bocanegra updated JCRVLT-30:
-----------------------------------

    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.

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

The default would be:
{noformat}
subPackageHandling = *;install
{noformat}

An example to exclude a subpackage from being installed would be:
{noformat}
subPackageHandling = *;install,somegroup:mypackage;ignore
{noformat}

^1^ Note: The difference between _install_ and _extract_ is the snapshot behavior. _extract_
does not create snapshots, _install_ does.

  was:
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.

{noformat}
subPackageHandling := instruction { "," instruction };
instruction := packageIdFilter { ";" option }
packageIdFilter := "*" | ( groupName [ ":" packageName ] );
option := "install" | "extract" | "ignore";  ^1^
{noformat}

The default would be:
{noformat}
subPackageHandling = *;install
{noformat}

An example to exclude a subpackage from being installed would be:
{noformat}
subPackageHandling = *;install,somegroup:mypackage;ignore
{noformat}

^1^ Note: The difference between _install_ and _extract_ is the snapshot behavior. _extract_
does not create snapshots, _install_ does.


> Allow package definition to specify recursive install behavior
> --------------------------------------------------------------
>
>                 Key: JCRVLT-30
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-30
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>
> 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.
> {noformat}
> subPackageHandling := instruction { "," instruction };
> instruction := packageIdFilter { ";" option }
> packageIdFilter := packageNameFilter | groupNameFilter ":" packageNameFilter;
> groupNameFilter := "*" | groupName;
> packageNameFilter := "*" | packageName;
> option := "install" | "extract" | "add" | "ignore";
> {noformat}
> The default would be:
> {noformat}
> subPackageHandling = *;install
> {noformat}
> An example to exclude a subpackage from being installed would be:
> {noformat}
> subPackageHandling = *;install,somegroup:mypackage;ignore
> {noformat}
> ^1^ Note: The difference between _install_ and _extract_ is the snapshot behavior. _extract_
does not create snapshots, _install_ does.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message