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

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

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

Guillaume Nodet resolved KARAF-448.
-----------------------------------

    Resolution: Fixed

https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commit;h=f1f2f1b5c8fdcfe8e4d3bd901002aee8b78d1322
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commit;h=0581f0786340960a4f28dccc25fb6660ea620a18

> 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, 3.0.1
>            Reporter: Andreas Pieber
>            Assignee: Guillaume Nodet
>             Fix For: 2.4.0, 3.0.2
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)