Stanbol
  1. Stanbol
  2. STANBOL-924

Make sure that Stanbol Commons, Entityub and Enhancer Bundles do import exported package

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: commons-0.11.0
    • Fix Version/s: 0.12.0
    • Component/s: Commons, Enhancer, Entityhub
    • Labels:
      None

      Description

      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

        Issue Links

          Activity

          Hide
          Rupert Westenthaler added a comment -

          marking this as resolved (http://svn.apache.org/r1461498) because commons, entityhub and enhancer where updated accordingly and those three components are also the one used within an embedded OSGI environment

          Show
          Rupert Westenthaler added a comment - marking this as resolved ( http://svn.apache.org/r1461498 ) because commons, entityhub and enhancer where updated accordingly and those three components are also the one used within an embedded OSGI environment
          Hide
          Rupert Westenthaler added a comment -

          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

          Show
          Rupert Westenthaler added a comment - 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

            People

            • Assignee:
              Rupert Westenthaler
              Reporter:
              Rupert Westenthaler
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development