karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KARAF-448) Make scanning for MANIFEST.MF in jar consistent between osgi:install and feature:install
Date Tue, 20 May 2014 22:22:38 GMT

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

Guillaume Nodet updated KARAF-448:
----------------------------------

    Affects Version/s: 3.0.1
        Fix Version/s:     (was: 4.0.0)
                       3.0.2
                       2.4.0
             Assignee: Guillaume Nodet

The behavior is different with 4.x already.

> 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)

Mime
View raw message