Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AF2E7200AE3 for ; Wed, 4 May 2016 10:23:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id ADF04160A02; Wed, 4 May 2016 10:23:14 +0200 (CEST) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E15121609F1 for ; Wed, 4 May 2016 10:23:13 +0200 (CEST) Received: (qmail 55844 invoked by uid 500); 4 May 2016 08:23:08 -0000 Mailing-List: contact user-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@karaf.apache.org Delivered-To: mailing list user@karaf.apache.org Received: (qmail 55834 invoked by uid 99); 4 May 2016 08:23:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 May 2016 08:23:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A077E1804D6 for ; Wed, 4 May 2016 08:23:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id FWjZ1X-ioQeq for ; Wed, 4 May 2016 08:23:04 +0000 (UTC) Received: from mail-lf0-f44.google.com (mail-lf0-f44.google.com [209.85.215.44]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 749485FDE6 for ; Wed, 4 May 2016 08:23:03 +0000 (UTC) Received: by mail-lf0-f44.google.com with SMTP id y84so50999455lfc.0 for ; Wed, 04 May 2016 01:23:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=kJrayufYYhry7dJwng07I5vqMdF7KJOPD4EN1xPgu2A=; b=A5yw/IN1D9j7+ULvTne4tLY6kJj6VkQoSAMzARMp2Q58wXr/dxH/bKXDjd5lQoV1O/ jRpvr2gF1Fp4dXnxLxJm3p8bnYdFL7I5oYDRu8e+hP2zfhJbvDe8aB/arVVMXbeiiDUu iSztyQU0N9Zkws43VqmZkCbSL1ehaY3gJH9jBmb8Pan0iicRMDwVYvGUZiX254vnmJWg f8DR/kaLwbS4SG1iA/z8uDyAYy0stKI1hB+ljC7g1CPuwXaZzMOS3HBUmyhsq8d8aui4 DN4kwXqPjNfYHXytS0HQqa390ZOxIUjSSOXVxWqYmWJSGjHSB+ioXOBNfKEFe7/if97B K6mA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=kJrayufYYhry7dJwng07I5vqMdF7KJOPD4EN1xPgu2A=; b=XkfwnjHyTM+9qfGUUi2IkyHdHIV4xp0rllr9dq+Hk/GZSbZUAMmt2Pz+7q7/pOnR2Y fxr9Eg9xo2no1hWxl8kdSZYhhAMlIZ/xqiCD4XJ4wjB7Mmk1cGbG3BoS4+BpItgaClQP OKrsgGmdL8DNMQbEQo4xSfRrEWQuxepoQeu5wM4t0IBk/r/q9lA+JO2NsS/nS4Cx4JYN 0jYuFIoWZzxnUV0eB2ESqpUdf1xQgUpvJQydLHbJ/Uz8qmgSCtwm/ooogLhX5gJn2piT w3dm6DeUUwY9JLJxSENeKUev4T/JCzIB4yHJo4xIz9qJGAosqKIviHdxho5w88Dld+fL dBkg== X-Gm-Message-State: AOPr4FUdR/VOQvvkbCRph70TFN754n3cgX6fHMZUo/xIg7MV01VTjA2Mp428uMtcsh4VVlf0Gm6SMi+A0l6Jnw== X-Received: by 10.112.162.169 with SMTP id yb9mr3504550lbb.70.1462350182030; Wed, 04 May 2016 01:23:02 -0700 (PDT) MIME-Version: 1.0 References: <5729ACCC.6090304@nanthrax.net> In-Reply-To: <5729ACCC.6090304@nanthrax.net> From: Cristiano Costantini Date: Wed, 04 May 2016 08:22:52 +0000 Message-ID: Subject: Re: Installing feature bundles anyway To: user@karaf.apache.org Content-Type: multipart/alternative; boundary=089e01160092232f1a0531ffef1c archived-at: Wed, 04 May 2016 08:23:14 -0000 --089e01160092232f1a0531ffef1c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi JB, thanks, I've tried but the option -t but it only report the same error (i.e. "Error executing command: Unable to resolve root: missing requirement [root] ....") as when I try to install the feature, leaving no bundle installed. If I want to debug more deeply where is the problem, I now need to run feature:info and install manually each bundle of the feature to find (with the "haders" command) who is having problem... The -c option was very useful in this condition and allowed me to quickly bundles from non working features and finding solutions to the issues... Is there any alternative to force installation of the bundles included in a feature? Il giorno mer 4 mag 2016 alle ore 10:11 Jean-Baptiste Onofr=C3=A9 < jb@nanthrax.net> ha scritto: > Hi, > > you can use -t to simulate. > > By default, the feature resolver will leave the bundles & features > installed before the failure. > > Regards > JB > > On 05/04/2016 09:42 AM, Cristiano Costantini wrote: > > Hello All, > > in the previous version of Karaf I was using (2.4.0) it was possible to > > install the bundles of a Features even if it cannot be started, using > > the option -c (--no-clean): > > > > karaf@root> features:install --help > > DESCRIPTION > > features:install > > > > Installs a feature with the specified name and version. > > > > SYNTAX > > features:install [options] feature > > > > ARGUMENTS > > feature > > The name and version of the features to install. A > > feature id looks like name/version. The version is optional. > > > > OPTIONS > > * -c, --no-clean* > > * Do not uninstall bundles on failure* > > -r, --no-auto-refresh > > Do not automatically refresh bundles > > -v, --verbose > > Explain what is being done > > --help > > Display this help message > > -s, --no-auto-start > > Do not automatically start bundles > > > > > > The option is no more available on Karaf 4.0.4, is there any other way > > to force installation of bundles included in a feature? > > > > Thank you, > > Cristiano > > > > -- > Jean-Baptiste Onofr=C3=A9 > jbonofre@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > --089e01160092232f1a0531ffef1c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi JB,
thanks, I've tried but the option -t but it= only report the same error (i.e. "Error executing command: Unable to = resolve root: missing requirement [root] ....") as when I try to insta= ll the feature, leaving no bundle installed.

If I = want to debug more deeply where is the problem, I now need to run=C2=A0feature:info and install manually each bundle o= f the feature to find (with the "haders" command) who is having p= roblem...

The -c option was very useful in this= condition and allowed me to quickly bundles from non working features and = finding solutions to the issues...

Is there any alternative to force installati= on of the bundles included in a feature?




Il= giorno mer 4 mag 2016 alle ore 10:11 Jean-Baptiste Onofr=C3=A9 <jb@nanthrax.net> ha scritto:
Hi,

you can use -t to simulate.

By default, the feature resolver will leave the bundles & features
installed before the failure.

Regards
JB

On 05/04/2016 09:42 AM, Cristiano Costantini wrote:
> Hello All,
> in the previous version of Karaf I was using (2.4.0) it was possible t= o
> install the bundles of a Features even if it cannot be started, using<= br> > the option -c (--no-clean):
>
> karaf@root> features:install --help
> DESCRIPTION
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 features:install
>
> Installs a feature with the specified name and version.
>
> SYNTAX
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 features:install [options] feature >
> ARGUMENTS
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 feature
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 The name= and version of the features to install. A
> feature id looks like name/version. The version is optional.
>
> OPTIONS
> *=C2=A0 =C2=A0 =C2=A0 =C2=A0 -c, --no-clean*
> *=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Do not uninst= all bundles on failure*
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -r, --no-auto-refresh
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Do not a= utomatically refresh bundles
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -v, --verbose
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Explain = what is being done
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --help
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Display = this help message
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -s, --no-auto-start
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Do not a= utomatically start bundles
>
>
> The option is no more available on Karaf 4.0.4, is there any other way=
> to force installation of bundles included in a feature?
>
> Thank you,
> Cristiano
>

--
Jean-Baptiste Onofr=C3=A9
jbonofre@apache.or= g
h= ttp://blog.nanthrax.net
Talend - http://www.talend.com
--089e01160092232f1a0531ffef1c--