karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Updated] (KARAF-448) Make scanning for MANIFEST.MF in jar consistent between osgi:install and feature:install
Date Mon, 11 Jul 2011 09:02:01 GMT

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

Jean-Baptiste Onofré updated KARAF-448:
---------------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.1.0
                   3.0.1

> 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.1, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message