• Intro Headers Instructions Macros Commands
  • Fork me on GitHub
    • Introduction
    • How to install bnd
    • Guided Tour
    • Guided Tour Workspace & Projects
    • Concepts
    • Best practices
    • Build
    • Project Setup
    • Generating JARs
    • Versioning
    • Baselining
    • Service Components
    • Metatype
    • Contracts
    • Bundle Annotations
    • Accessor Properties
    • SPI Annotations
    • Resolving Dependencies
    • Launching
    • Startlevels
    • Testing
    • Testing with Launchpad
    • Packaging Applications
    • JPMS Libraries
    • Wrapping Libraries to OSGi Bundles
    • Generating Documentation
    • Commands
    • For Developers
    • Tips for Windows users
    • Tools bound to bnd
    • Headers
    • Instruction Reference
    • Instruction Index
    • Macro Reference
    • Macro Index
    • Plugins
    • External Plugins
    • Settings
    • Errors
    • Warnings
    • Frequently Asked Questions
  • -runframeworkrestart BOOLEAN

    Any bundle can stop the framework. After stopping, the launcher receives a notification and normally exit the process with System.exit. In some cases, usually testing, it is necessary to do a restart in the local VM.

    If -runframeworkrestart is set to true, the launcher will not do a hard exit after the framework is stopped, but will restart the framework after doing the normal clean up.

    The launcher keeps a system property launcher.framework.restart.count that is set to the iteration, it is initially zero.

    • GitHub