Google Git
Sign in
apache / felix-dev / 69b73354f8fe8385d0b60dbc93ec7cd46ff370bc
commit69b73354f8fe8385d0b60dbc93ec7cd46ff370bc[log] [tgz]
authorGuillaume Nodet <gnodet@gmail.com>Tue Apr 29 22:49:46 2025 +0200
committerStefan Bischof <bipolis@bipolis.org>Wed Apr 30 08:58:41 2025 +0200
tree4372b8728b9caaca50b5c9c7de83d31ce51dedd1
parentd95c1ae6e5e614b4f7731a1a6cc4014a3bea6853 [diff]
Make Pipe.setCurrentPipe public to fix interruption handling in nested shells

This change makes the setCurrentPipe method in the Pipe class public to allow proper handling of interruption signals in nested shells. This is needed to fix an issue in JLine where Ctrl+C doesn't properly interrupt commands running in a nested shell.

The issue occurs when a user starts a shell session, then runs the 'sh' command to create a nested shell, and then runs a command like 'ttop' in that nested shell. When the user presses Ctrl+C to interrupt the 'ttop' command, the interruption signal is caught by the parent shell but not properly propagated to the child shell.

By making setCurrentPipe public, we allow the nested shell to clear the current pipe before creating a child shell and restore it afterward, ensuring that interruption signals are properly propagated.

See: https://github.com/jline/jline3/issues/1143
1 file changed
tree: 4372b8728b9caaca50b5c9c7de83d31ce51dedd1
  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. .gitignore
  40. check_staged_release.sh
  41. CODE_OF_CONDUCT.md
  42. CONTRIBUTING.md
  43. LICENSE
  44. README.md
  45. 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.