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 1B437EDF9 for ; Tue, 12 Mar 2013 06:15:18 +0000 (UTC) Received: (qmail 17261 invoked by uid 500); 12 Mar 2013 06:15:16 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 17011 invoked by uid 500); 12 Mar 2013 06:15:16 -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 16323 invoked by uid 99); 12 Mar 2013 06:15:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 06:15:13 +0000 Date: Tue, 12 Mar 2013 06:15:13 +0000 (UTC) From: "Sahoo (JIRA)" To: dev@felix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FELIX-3966) Require-Bundle header is not parsed correctly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sahoo created FELIX-3966: ---------------------------- Summary: Require-Bundle header is not parsed correctly Key: FELIX-3966 URL: https://issues.apache.org/jira/browse/FELIX-3966 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.2.0 Reporter: Sahoo Priority: Trivial Fix For: framework-4.4.0 It seems Felix is not detetcing a bad Require-Bundle header where as Knopfler is detecting it: Require-Bundle: bundle1, system.bundle; org.knopflerfish.framework; resolution:=optional A correct way to write above would be: Require-Bundle: bundle1, system.bundle;resolution:=optional, org.knopflerfish.framework; resolution:=optional -- 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