Google GitGoogle Git
Sign in
apache/felix-dev/b77e43c5b75a385e13157ae2ef44a61400ad19aa
commit
b77e43c5b75a385e13157ae2ef44a61400ad19aa
[log]
author
Paul Rütter <paul@blueconic.com>
Thu Sep 03 16:56:01 2026 +0200
committer
Paul Rütter <paul@blueconic.com>
Thu Sep 03 16:56:01 2026 +0200
tree
ab6e242dea0586fe68817b4c1582b7f13a329957
parent
049c7a355e2dbe417092b03917f1751e63db13e8 [diff]
Align metatype descriptions with the actual config defaults

Two attribute definitions in ConfigMetaTypeProvider disagreed with
JettyConfig, in both the Jetty 11 and the Jetty 12 bundle:

* org.apache.felix.https.jetty.renegotiateAllowed was described as
  "true by default", while isRenegotiationAllowed() defaults it to
  false. The default value of the attribute definition itself was
  already false, so only the description text was wrong.
* org.apache.felix.http.requestlog.osgi.format declared NCSA_FORMAT as
  its default value, while getRequestLogOSGiFormat() falls back to
  EXTENDED_NCSA_FORMAT. Since the attribute default is what a
  configuration UI pre-fills and persists on save, this could silently
  change the request log format from extended to plain NCSA.

The metatype now follows the code in both cases; no runtime default
changes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2 files changed
tree: ab6e242dea0586fe68817b4c1582b7f13a329957
  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.