Google GitGoogle Git
Sign in
apache/felix-dev/8a0efb9e8b82c9150320b5caa39b5a99443d6127
commit
8a0efb9e8b82c9150320b5caa39b5a99443d6127
[log]
author
Paul Rütter <paul@blueconic.com>
Sat Aug 29 22:45:38 2026 +0200
committer
Paul Rütter <paul@blueconic.com>
Sat Aug 29 22:45:38 2026 +0200
tree
46d45a2c95ecf6f5d6c54e0f74382f38ecf48e26
parent
a6002a674fa7583dccd525b4206c69196d8f4787 [diff]
Fix the TCK dependency ranges so the framework TCK can run

The OSGi Core TCK currently cannot resolve on any JDK, so framework.tck fails before
executing a single test. That is what hid the FilterImpl defects fixed in this branch,
and it also means CI cannot demonstrate the fix without repairing it.

Two ranges were left behind when assertj-core was bumped from 3.27.3 to 3.27.7 in
#478:

- tck.bndrun still required assertj-core [3.27.3,3.27.4), so the bndrun could not be
  resolved at all: "assertj-core;version=[3.27.3,3.27.4) Not found in [...
  assertj-core;version=3.27.7 ...]".
- assertj-core 3.27.7 imports net.bytebuddy [1.18.0,2.0.0) but byte-buddy was pinned
  at 1.17.5, so assertj-core then failed to start with an unresolved
  osgi.wiring.package requirement.

Also removes a duplicate junit-platform-launcher dependency, which Maven reports as a
malformed model and warns it may reject in future.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2 files changed
tree: 46d45a2c95ecf6f5d6c54e0f74382f38ecf48e26
  1. .github/
  2. bundlerepository/
  3. bundlerepository.osgi-ct/
  4. cm.json/
  5. configadmin/
  6. configadmin-plugins/
  7. configurator/
  8. connect/
  9. coordinator/
  10. dependencymanager/
  11. doap/
  12. eventadmin/
  13. examples/
  14. features/
  15. fileinstall/
  16. framework/
  17. framework.security/
  18. framework.tck/
  19. gogo/
  20. healthcheck/
  21. http/
  22. inventory/
  23. ipojo/
  24. log/
  25. log.extension/
  26. main/
  27. main.distribution/
  28. metatype/
  29. pom/
  30. resolver/
  31. rootcause/
  32. scr/
  33. scr-ext-anno/
  34. systemready/
  35. tools/
  36. utils/
  37. webconsole/
  38. webconsole-plugins/
  39. .asf.yaml
  40. .gitignore
  41. check_staged_release.sh
  42. CODE_OF_CONDUCT.md
  43. CONTRIBUTING.md
  44. LICENSE
  45. README.md
  46. 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 Core

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.
  • OSGi metrics /metrics/osgi - Collecting and publishing metrics related to OSGi applications
  • 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.