You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Christian Schneider (Updated) (JIRA)" <ji...@apache.org> on 2012/03/07 14:29:00 UTC

[jira] [Updated] (KARAF-448) Make scanning for MANIFEST.MF in jar consistent between osgi:install and feature:install

     [ https://issues.apache.org/jira/browse/KARAF-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider updated KARAF-448:
--------------------------------------

    Fix Version/s:     (was: 3.0.0)
    
> 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: karaf-core, karaf-shell
>    Affects Versions: 2.1.3, 2.2.0
>            Reporter: Andreas Pieber
>            Assignee: Andreas Pieber
>             Fix For: 3.1.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira