Return-Path: X-Original-To: apmail-karaf-dev-archive@minotaur.apache.org Delivered-To: apmail-karaf-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 066D210D90 for ; Wed, 11 Feb 2015 23:41:28 +0000 (UTC) Received: (qmail 77500 invoked by uid 500); 11 Feb 2015 23:41:27 -0000 Delivered-To: apmail-karaf-dev-archive@karaf.apache.org Received: (qmail 77452 invoked by uid 500); 11 Feb 2015 23:41:27 -0000 Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list dev@karaf.apache.org Received: (qmail 77440 invoked by uid 99); 11 Feb 2015 23:41:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2015 23:41:27 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cschneider111@gmail.com designates 209.85.192.48 as permitted sender) Received: from [209.85.192.48] (HELO mail-qg0-f48.google.com) (209.85.192.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2015 23:41:02 +0000 Received: by mail-qg0-f48.google.com with SMTP id a108so5439411qge.7 for ; Wed, 11 Feb 2015 15:39:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mcwtnY4/ozqTBCHshgA1qIqf26pKnUXZNmtc0wIsTbg=; b=Hcs85hk4QmgGCW5n2yKQr5HyAsrPXD0Z8E8YUJYUImJADFEb/NM69VEYrSWEPZpAbo 7/1YkN7puyAplrT6RBvkv23Y9H60DwGAxTyMM0EzpBm1Dpv60Kxyt/jNZUb617FzETA6 L440IKTl2fKl7GYhiCnKntuSnCDPuzgH9U5atjEB8a5mdfH08saNfHn/CZNGxRoKxqPp wKLRsyBmBuyl7Mg6mA+Uy7BbBxxUmglnYUp5ehlBp2T4XYLmrqjJ6A2hmUnir9StkIbl 8CNLEPLzRz8d8oLeK8Vr1BFDjATgGAviEIxMEPwa/Jbje1u+WS/AqYJQY1+WGA5wvW9L mJHw== X-Received: by 10.140.81.74 with SMTP id e68mr2467247qgd.41.1423697970585; Wed, 11 Feb 2015 15:39:30 -0800 (PST) Received: from [192.168.0.110] (HSI-KBW-46-223-17-135.hsi.kabel-badenwuerttemberg.de. [46.223.17.135]) by mx.google.com with ESMTPSA id e13sm2338969qaa.48.2015.02.11.15.39.29 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Feb 2015 15:39:30 -0800 (PST) Sender: Christian Schneider Message-ID: <54DBE82B.6020604@die-schneider.net> Date: Thu, 12 Feb 2015 00:39:23 +0100 From: Christian Schneider User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: dev@karaf.apache.org Subject: Re: Karaf 4.0 : new behaviour of the feature resolver References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Am 11.02.2015 um 22:02 schrieb Guillaume Nodet: > The breaking change is that features are now verified before being > installed. > In karaf < 4, there was no verification step, and the installation of the > feature was simply trying to install the bundles and start those. In most cases I like the verification. In some cases though especially when I build the deployment I sometimes want the bundles to be installed even if they do not even resolve. The reason is that it is easier to debug what is wrong when the bundles are in the system. So I would like to have an option to install even if the verification fails. Kind of like the option in karaf 2 and 3 where you leave the bundles installed in case of a failure. Doe that make sense? Christian -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com