[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-329) SystemBundle not added as MC module

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/browse/JBOSGI-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler updated JBOSGI-329:
----------------------------------

    Summary: SystemBundle not added as MC module  (was: SystemBundle added as MC module)


> SystemBundle not added as MC module
> -----------------------------------
>
>                 Key: JBOSGI-329
>                 URL: https://jira.jboss.org/browse/JBOSGI-329
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core Framework
>            Reporter: Thomas Diesler
>             Fix For:  JBossOSGi 1.0.x
>
>
> Currently we do not create OSGiPackageRequirements that map to system packages defined at the framework level. 
> In various places, especially in resolver integration, that leads to special workaround treatment when a bundle defines a requirement on a system package (possibly with a version qualifier)  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira