Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@karaf.apache.org
Date: Mon, 7 Feb 2011 21:00:57 +0000 (UTC)
From: "Andreas Pieber (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <155657374.704.1297112457445.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Created: (KARAF-448) Make scanning for MANIFEST.MF in jar
 consistent between osgi:install and feature:install
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Make scanning for MANIFEST.MF in jar consistent between osgi:install and feature:install
----------------------------------------------------------------------------------------

                 Key: KARAF-448
                 URL: https://issues.apache.org/jira/browse/KARAF-448
             Project: Karaf
          Issue Type: Improvement
          Components: console, runtime
    Affects Versions: 2.1.3, 2.2.0
            Reporter: Andreas Pieber
            Assignee: Andreas Pieber
             Fix For: 3.0.0


Currently osgi:install works if the MANIFEST.MF could not be found in first place of a jar and features:install fails in the same situation. First of all the behavior between those two commands should be made consistent; secondly they should not fail if the MANIFEST.MF couldn't be found on the first place but should rather log a warning and continue till one could be found.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira