Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Plug-in Start Levels to enable slf4j-2 logging #43

Merged
merged 1 commit into from
Aug 24, 2023

Commits on Aug 22, 2023

  1. Configure Plug-in Start Levels to enable slf4j-2 logging

    For all products this means that the implementation of the OSGi Service
    Loader Mediator Specification supplied by Eclipse-Platform, namly the
    'org.apache.aries.spifly.dynamic.bundle' bundle has to be auto-started
    at level two, like it is already done for the Eclipse SDK managed by
    Eclipse-Platform.
    
    All products that contain the slf4j.simple logging back-end, need to
    auto-start slf4j.simple as well.
    Additionally a VM-property is set to turn slf4j.simple off by default.
    A user can then configure it as desired by modifying/setting the
    corresponding system-properties in the eclipse.ini, as defined in the
    SimpleLogger doc:
    https://www.slf4j.org/api/org/slf4j/simple/SimpleLogger.html
    
    If a product uses the o.e.m2e.logback feature, and therefore logback as
    logging back-end, nothing needs to be done. The m2e.logback
    feature already performs all necessary configuration upon its
    installation.
    
    Fixes eclipse-packaging#27
    HannesWell committed Aug 22, 2023
    Configuration menu
    Copy the full SHA
    c76afaf View commit details
    Browse the repository at this point in the history