Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03B6FF237 for ; Fri, 14 Nov 2014 16:12:35 +0000 (UTC) Received: (qmail 79954 invoked by uid 500); 14 Nov 2014 16:12:34 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 79908 invoked by uid 500); 14 Nov 2014 16:12:34 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 79884 invoked by uid 99); 14 Nov 2014 16:12:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Nov 2014 16:12:34 +0000 Date: Fri, 14 Nov 2014 16:12:34 +0000 (UTC) From: "Christian Schneider (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-8051) feature camel-core does not install in karaf 4 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Christian Schneider created CAMEL-8051: ------------------------------------------ Summary: feature camel-core does not install in karaf 4 Key: CAMEL-8051 URL: https://issues.apache.org/jira/browse/CAMEL-8051 Project: Camel Issue Type: Bug Components: camel-core, osgi Affects Versions: 2.14.0 Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 2.15.0 feature:repo-add camel 2.15-SNAPSHOT feature:install -v camel-core Karaf then tries to install the karaf shell console from karaf 2.4.0 which of course fails. I first removed the reference to the karaf spring feature repo which transitively imported the karaf standard feature. After that change it could not resolve the package: (org.apache.felix.service.command)(version>=0.14.0)(!(version>=1.0.0) The problem here was that we forgot status=provisional in the import. -- This message was sent by Atlassian JIRA (v6.3.4#6332)