Return-Path: <user-return-15192-archive-asf-public=cust-asf.ponee.io@karaf.apache.org>
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 D6131200B81
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue, 30 Aug 2016 07:05:03 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id D47A4160AC9; Tue, 30 Aug 2016 05:05:03 +0000 (UTC)
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 294C2160AB8
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 30 Aug 2016 07:05:03 +0200 (CEST)
Received: (qmail 83973 invoked by uid 500); 30 Aug 2016 05:05:02 -0000
Mailing-List: contact user-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@karaf.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@karaf.apache.org>
List-Post: <mailto:user@karaf.apache.org>
List-Id: <user.karaf.apache.org>
Reply-To: user@karaf.apache.org
Delivered-To: mailing list user@karaf.apache.org
Received: (qmail 83963 invoked by uid 99); 30 Aug 2016 05:05:02 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Aug 2016 05:05:02 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D83311A08D9
	for <user@karaf.apache.org>; Tue, 30 Aug 2016 05:05:01 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 3.472
X-Spam-Level: ***
X-Spam-Status: No, score=3.472 tagged_above=-999 required=6.31
	tests=[FORGED_HOTMAIL_RCVD2=1.187, RCVD_IN_DNSWL_NONE=-0.0001,
	SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled
Received: from mx2-lw-eu.apache.org ([10.40.0.8])
	by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
	with ESMTP id Ir3Op21s1ZNJ for <user@karaf.apache.org>;
	Tue, 30 Aug 2016 05:04:59 +0000 (UTC)
Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43])
	by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id 58C175FAE3
	for <user@karaf.apache.org>; Tue, 30 Aug 2016 05:04:59 +0000 (UTC)
Received: from mben.nabble.com (unknown [162.253.133.72])
	by mwork.nabble.com (Postfix) with ESMTP id 8481243A69F8B
	for <user@karaf.apache.org>; Mon, 29 Aug 2016 22:04:58 -0700 (MST)
Date: Mon, 29 Aug 2016 22:04:58 -0700 (MST)
From: oski_bear <dariushamiri@hotmail.com>
To: user@karaf.apache.org
Message-ID: <1472533498541-4047753.post@n3.nabble.com>
Subject: Karaf 4.0.5 prerequisite feature not installed with correct version
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Tue, 30 Aug 2016 05:05:04 -0000

I'm having a hard time with feature installation in Karaf 4.0.5. The latest
issue seems to be that Karaf 4.0.5 disregards the version specified for a
prerequisite feature. E.g.

<features name="my-features-${project.version}"
xmlns="http://karaf.apache.org/xmlns/features/v1.4.0">
  <feature name="feature-a" version="${project.version}" description="Some
feature">
    <feature prerequisite="true"
version="3.2.14.RELEASE_1">spring-orm</feature>
    ...
  </feature>
</features>

After the container starts up I see that multiple versions of the spring
feature are installed instead of just the 3.2.14.RELEASE_1 version that I
specified. Seems like a bug.

Also I've noticed:
* The karaf-maven-plugin completely disregards the order specified in the
<bootFeatures> section of its configuration. E.g. try configuring the
<bootFeatures> section of the karaf-maven-plugin, build your custom
container, then scratch your head at the seemingly completely random order
of the boot features property in the org.apache.karaf.features.cfg file. Why
can't it just generate the file with the boot features in the same order I
specified in the plugin? Can I fix this? Is there a workaround?
* What's up with the seemingly random restarts of the container and the
endless stream of "The specified feature: blah version blah is already
installed" messages? Why does this happen? If it's normal or expected
behavior what's the point of these annoying messages? How can I prevent this
situation?
* Why is that sometimes when features fail to install the shell becomes
completely unresponsive?

I don't remember installing and defining features being this frustrating in
karaf 2.x.



--
View this message in context: http://karaf.922171.n3.nabble.com/Karaf-4-0-5-prerequisite-feature-not-installed-with-correct-version-tp4047753.html
Sent from the Karaf - User mailing list archive at Nabble.com.