You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@celix.apache.org by "Menno van der Graaf (JIRA)" <ji...@apache.org> on 2016/01/26 17:14:40 UTC

[jira] [Updated] (CELIX-342) Bundle Manifest unused

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

Menno van der Graaf updated CELIX-342:
--------------------------------------
    Priority: Minor  (was: Trivial)

> Bundle Manifest unused
> ----------------------
>
>                 Key: CELIX-342
>                 URL: https://issues.apache.org/jira/browse/CELIX-342
>             Project: Celix
>          Issue Type: Improvement
>          Components: Framework
>            Reporter: Menno van der Graaf
>            Priority: Minor
>
> After some confusion during a debug session, i looked into why the "bundle->manifest" pointer was always NULL. It turns out this is initialized at creation, then never assigned. Yet the framework works fine? Apparently the manifest files distributed in each bundle ARE used, by the bundle revision. Each bundle revision holds a manifest, that is then used for module creation and data acquisition.
> The question then remains, is this construct correct? in which case I would propose to delete the "bundle->manifest" field, since it causes confusion (and Celix could do with a bit less confusion).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)