Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 259191024C for ; Tue, 18 Feb 2014 05:44:30 +0000 (UTC) Received: (qmail 22753 invoked by uid 500); 18 Feb 2014 05:44:28 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 22716 invoked by uid 500); 18 Feb 2014 05:44:23 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 22707 invoked by uid 99); 18 Feb 2014 05:44:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Feb 2014 05:44:19 +0000 Date: Tue, 18 Feb 2014 05:44:19 +0000 (UTC) From: "Tobias Bocanegra (JIRA)" To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (JCRVLT-30) Allow package definition to specify recursive install behavior MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)