[jira] [Resolved] (FELIX-6313) Atomos must handle when modules names and bundle symbolic names are different

["Tom Watson (Jira)" <ji...@apache.org>]

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

Tom Watson resolved FELIX-6313.
-------------------------------
    Resolution: Fixed

> Atomos must handle when modules names and bundle symbolic names are different
> -----------------------------------------------------------------------------
>
>                 Key: FELIX-6313
>                 URL: https://issues.apache.org/jira/browse/FELIX-6313
>             Project: Felix
>          Issue Type: Improvement
>          Components: Atomos
>            Reporter: Tom Watson
>            Priority: Major
>
> Atomos converts module meta-data to bundle meta-data when a module is discovered which does not have a bundle manifest.  The module requires are converted to osgi.wiring.bundle (Require-Bundle) requirements.  But this has an assumption that the required module has a bundle symbolic name that equals the required module name.
> This is not always going to be the case.  For example, it appears many of the jakarta EE 9 API modules will be using a different bundle symbolic name from their (automatic) module name.
> This is an unfortunate complication, but Atomos could discover this mismatch and map the module requires to use the real BSN of the required module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)