Return-Path: X-Original-To: apmail-felix-dev-archive@www.apache.org Delivered-To: apmail-felix-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 065F9DF68 for ; Fri, 14 Sep 2012 11:22:15 +0000 (UTC) Received: (qmail 40682 invoked by uid 500); 14 Sep 2012 11:22:14 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 40258 invoked by uid 500); 14 Sep 2012 11:22:09 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 40211 invoked by uid 99); 14 Sep 2012 11:22:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Sep 2012 11:22:07 +0000 Date: Fri, 14 Sep 2012 22:22:07 +1100 (NCT) From: "Tan-Vinh Nguyen (JIRA)" To: dev@felix.apache.org Message-ID: <1195104299.79858.1347621727709.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (FELIX-3664) Uninstall with bundle range MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tan-Vinh Nguyen created FELIX-3664: -------------------------------------- Summary: Uninstall with bundle range Key: FELIX-3664 URL: https://issues.apache.org/jira/browse/FELIX-3664 Project: Felix Issue Type: Wish Components: Gogo Shell Reporter: Tan-Vinh Nguyen Priority: Minor Assume you have installed bundles from 300 up to 350. Usually to uinstall a bundle it is felix:uninstall 300 I suggest to extend the uninstall command with a bundle range, e.g. 300-350, that uninstall all bundles within the range. Usually i do a bash this echo output for i in $(seq 300 350); do echo $i; done and piped it to the gogo shell. It would be a great improvement. What does the Felix team think of it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira