Google Git
Sign in
apache / felix / a13ea8ea177933e2911b14e1de55fff4e5196927
commita13ea8ea177933e2911b14e1de55fff4e5196927[log] [tgz]
authorTom Watson <tjwatson@apache.org>Tue Jan 14 21:31:18 2020 +0000
committerTom Watson <tjwatson@apache.org>Tue Jan 14 21:31:18 2020 +0000
treef6f7d9ef532eb5553717cebeb42dd67d0d7ec7d4
parentf423e17c3c8979a9ee3636fc8ca233309d83a10e [diff]
FELIX-6212 : Add testcase and fix reexport uses constraint check

When an exporter of a split package requires multiple bundles that also
export the split package and that bundle does a reexport on one of the
parts it can cause resolution issues for uses constraints.

The actual problem is with reexport itself.  The reexporting bundle does
not have to also export the package to cause the issue.  The problem is
that each part of the package pulled in from the require-reexport is
checked in isolation with the using bundles wire to the same package
name.  This is incorrect because that is only a subset of the actual
used package from the perspective of the exported package that is using
the split package.

The fix is to record all the package  parts for the split used package
from the wiring of the bundle exporting the package that uses the split
package.  That way during the compatibility check we can accurately use
the set of sources for the split package that the exporting bundle is
using.

git-svn-id: https://svn.apache.org/repos/asf/felix/trunk@1872796 13f79535-47bb-0310-9956-ffa450edef68
2 files changed
tree: f6f7d9ef532eb5553717cebeb42dd67d0d7ec7d4
  1. bundlerepository/
  2. bundlerepository.osgi-ct/
  3. configadmin/
  4. configadmin-plugins/
  5. configurator/
  6. connect/
  7. converter/
  8. coordinator/
  9. dependencymanager/
  10. deploymentadmin/
  11. deviceaccess/
  12. doap/
  13. eventadmin/
  14. examples/
  15. fileinstall/
  16. fileinstall-plugins/
  17. framework/
  18. framework.security/
  19. gogo/
  20. healthcheck/
  21. http/
  22. httplite/
  23. installers/
  24. inventory/
  25. io/
  26. ipojo/
  27. jaas/
  28. jmood/
  29. jmxintrospector/
  30. log/
  31. log.extension/
  32. logback/
  33. main/
  34. main.distribution/
  35. metatype/
  36. mishell/
  37. mosgi/
  38. org.apache.felix.daemon/
  39. org.osgi.service.obr/
  40. pom/
  41. prefs/
  42. resolver/
  43. rootcause/
  44. scr/
  45. scr-compat/
  46. scr-ext-anno/
  47. service/
  48. shell/
  49. shell.gui/
  50. shell.gui.plugin/
  51. shell.remote/
  52. shell.tui/
  53. systemready/
  54. threaddump/
  55. tools/
  56. transaction/
  57. upnp/
  58. useradmin/
  59. utils/
  60. webconsole/
  61. webconsole-l10n/
  62. webconsole-plugins/
  63. wireadmin/
  64. .gitignore
  65. check_staged_release.sh
  66. README.md
  67. stage_existing_artifact.sh
README.md

Apache Felix

The Apache Felix project is a collection of semi-related OSGi sub-projects that build and release individually.

Felix Framework

The flagship project is the Apache Felix Framework which implements the OSGi Core R7 specification. The /framework directory contains the source and build tree for the OSGi-compliant framework implementation.

Directly related projects:

  • main /main* - provides an executable jar that launches the Felix framework.

OSGi Compendium

Several sub-projects cover various OSGi Compendium specifications such as:

Extra Features

Several projects provide extra features to an OSGi runtime.

  • bundle repository /bundlerepository - Bundle repository service.
  • connect /connect - A service registry that enables OSGi style service registry programs without using an OSGi framework.
  • dependency manager /dependencymanager - A versatile java API, allowing to declaratively register, acquire, and manage dynamic OSGi services.
  • fileinstall /fileinstall* - A utility to automatically install bundles from a directory.
  • gogo /gogo - A command line shell, runtime and set of base commands for interacting with and introspecting an OSGi framework.
  • health checks /healthcheck/* - An extensible framework to monitor the status of the OSGi container at runtime. (contains systemready)
  • inventory /inventory - Provides some mechanisms to get the current state of the system and therefore provides an inventory of the system.
  • ipojo /ipojo - A service component runtime aiming to simplify OSGi application development.
  • jaas support /jaas - Bundle to simplify JAAS usage within OSGi environment.
  • logback /logback - A simple integration of the OSGi R7 Log (1.4) service to Logback backend.
  • rootcause /rootcause - Finding the root cause of problems with OSGi declarative services components.
  • utils /utils - Utility classes for OSGi (intended for embedding within other bundles.)
  • webconsole /webconsole* - Web Based Management Console for OSGi Frameworks.
  • and many other OSGi things

Build tools

The /tools directory contains various build tools.

  • maven-bundle-plugin /tools/maven-bundle-plugin - A maven plugin for building OSGi bundles.
  • osgicheck-maven-plugin /tools/osgicheck-maven-plugin - Maven plugin for checking several OSGi aspects of your project.