[
https://issues.apache.org/jira/browse/FELIX-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch resolved FELIX-3065.
-------------------------------------
Resolution: Won't Fix
Closing as working as designed, the blueprint support specifically adds an
import for "!org.osgi.service.blueprint" to the manifest - if you don't want
this behaviour you can turn it off by using:
<Import-Package>!org.osgi.service.blueprint,*</Import-Package> as mentioned by
Felix.
> Make inclusion of "Import-Package:org.osgi.service.blueprint" optional
> -----------------------------------------------------------------------
>
> Key: FELIX-3065
> URL: https://issues.apache.org/jira/browse/FELIX-3065
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.5
> Environment: Any
> Reporter: Matt Bishop
>
> The maven-bundle-plugin autoadds an
> "Import-Package:org.osgi.service.blueprint" directive in the manifest. This
> makes sense, as you want your blueprint dependencies to be manged once
> blueprint is loaded.
> However, if one is using Gemini for blueprint service, this package is never
> exported. This means that the bundle will never be loaded. I have filed a bug
> with Gemini on this topic already, but it leads developers to workarounds
> like this in the bundle <configuration> section:
> <Import-Package>
> javax.inject,
> org.apache.commons.lang;version="[2.6,3)",
> org.slf4j;version="[1.6,2)",
> !org.osgi.service.blueprint
> </Import-Package>
> This is a pain because you have to explicitly declare every import package
> manually rather than having the bundle plugin work it's auto-import-package
> magic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
