Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: qos-ch/logback
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v_1.5.25
Choose a base ref
...
head repository: qos-ch/logback
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v_1.5.26
Choose a head ref
  • 9 commits
  • 41 files changed
  • 2 contributors

Commits on Jan 17, 2026

  1. start work on 1.5.26-SNAPSHOT 

    Signed-off-by: ceki <[email protected]>
    @ceki
    ceki committed Jan 17, 2026
    Configuration menu
    Copy the full SHA
    6d52744 View commit details
    Browse the repository at this point in the history

  2. fix javadoc errors

    @ceki
    ceki committed Jan 17, 2026
    Configuration menu
    Copy the full SHA
    033aba4 View commit details
    Browse the repository at this point in the history

Commits on Jan 19, 2026

  1. mention country only, add missing 2016-03-29 

    Signed-off-by: Ceki Gulcu <[email protected]>
    @ceki
    ceki committed Jan 19, 2026
    Configuration menu
    Copy the full SHA
    420d67c View commit details
    Browse the repository at this point in the history

Commits on Jan 23, 2026

  1. Do not use javax.naming namespace in the catch block, so that Logback… 

    … can be used without requiring the javax.naming module (#1004)

The InsertFromJNDIModelHandler is usually created when using Logback, but only used when JNDI is used in the logging configuration. Catching the javax.naming.NamingException will automatically resolve the class when the InsertFromJNDIModelHandler class is used, throwing an exception when it is not present.

By catching the generic Exception, unless JNDI or SMTP are used, the javax.naming module is not required now.

Signed-off-by: Marius Hanl <[email protected]>
    @Maran23
    Maran23 authored Jan 23, 2026
    Configuration menu
    Copy the full SHA
    00d272f View commit details
    Browse the repository at this point in the history

Commits on Jan 24, 2026

  1. version information is self declared by modules. 

    Due to cyclical dependency reasons, it is not possible for VersionUtil in
logback-core to querty properties files located in logback-classic. It
follows that, logback-classic deplicated some code found in VersionUtil
in ClassicVersionUtil.

Signed-off-by: ceki <[email protected]>
    @ceki
    ceki committed Jan 24, 2026
    Configuration menu
    Copy the full SHA
    7a8f0b6 View commit details
    Browse the repository at this point in the history

  2. modify VersionCheckTest to use logback-core 1.5.25 

    Signed-off-by: ceki <[email protected]>
    @ceki
    ceki committed Jan 24, 2026
    Configuration menu
    Copy the full SHA
    8bd5660 View commit details
    Browse the repository at this point in the history

  3. move VersionUtil.getCoreVersionBySelfDeclaredProperties to CoreVersio… 

    …nUtil

Signed-off-by: ceki <[email protected]>
    @ceki
    ceki committed Jan 24, 2026
    Configuration menu
    Copy the full SHA
    4368333 View commit details
    Browse the repository at this point in the history

Commits on Jan 25, 2026

  1. refactoring based on usage in logback-access 

    Signed-off-by: ceki <[email protected]>
    @ceki
    ceki committed Jan 25, 2026
    Configuration menu
    Copy the full SHA
    d38a3e2 View commit details
    Browse the repository at this point in the history

  2. prepare release 1.5.26 

    Signed-off-by: ceki <[email protected]>
    @ceki
    ceki committed Jan 25, 2026
    Configuration menu
    Copy the full SHA
    33deb54 View commit details
    Browse the repository at this point in the history
Loading