[
https://issues.apache.org/jira/browse/STANBOL-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577733#comment-13577733
]
Rupert Westenthaler commented on STANBOL-924:
---------------------------------------------
based on [1] the Bundle Plugin for Maven should ensure this
>From the documentation:
> * <Import-Package> is assumed to be "*", which imports everything referred to
> by the bundle content, but not contained in the bundle.
> Any exported packages are also imported by default, to ensure a consistent
> class space.
However when looking at the generated MANIFEST files this is not the case.
Adding explicit Import-Package seams to be the only way to ensure that the
manifest imports all exported packages.
Maybe this is related to some configuration issue of the Plugin
> Make sure that Stanbol Bundles do import exported package
> ---------------------------------------------------------
>
> Key: STANBOL-924
> URL: https://issues.apache.org/jira/browse/STANBOL-924
> Project: Stanbol
> Issue Type: Bug
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> OSGI bundles should import exported packages to avoid classpath segmentation
> as described by [1]. While this is typically no issue when working within an
> OSGI environment it can get really troublesome when Stanbol is used in an
> embedded OSGI environment as described by STANBOL-772
> [1] http://blog.osgi.org/2007/04/importance-of-exporting-nd-importing.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
