You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Grzegorz Grzybek <gr...@gmail.com> on 2021/12/18 18:14:25 UTC
[ANN] Pax Logging 2.0.13 and 1.11.12 released
Hello
Pax Logging 2.0.13 and 1.11.12 have been released with two upgrades:
- Log4j2 2.17.0
- Logback 1.2.9
These are the latest versions of the dependencies as of December 18th 2021.
The changelogs are:
- 2.0.13:
https://github.com/ops4j/org.ops4j.pax.logging/milestone/75?closed=1
- 1.11.12:
https://github.com/ops4j/org.ops4j.pax.logging/milestone/76?closed=1
kind regards
Grzegorz Grzybek
[ANN] Pax Logging 2.0.14, 1.11.13 and 1.10.9 released
Posted by Grzegorz Grzybek <gr...@gmail.com>.
Hello
Pax Logging 2.0.14, 1.11.13 and 1.10.9 have been released with two upgrades:
- Log4j2 2.17.1
- Logback 1.2.10
These are the latest versions of the dependencies as of December 30th 2021.
Additionally, 2.0.14 and 1.11.13 contain new configuration property:
"org.ops4j.pax.logging.syncJULFormatter" (defaults to "true") which
controls the usage of `java.util.logging.SimpleFormatter` inside Pax
Logging's JUL Handler. By default, there's a single formatter with
synchronization. When this property is set to "false", new instance is
created for each event being handled - this is special system/context
property to be used in Payara server where some deadlocks were observed.
The changelogs are:
- 2.0.14:
https://github.com/ops4j/org.ops4j.pax.logging/milestone/78?closed=1
- 1.11.13:
https://github.com/ops4j/org.ops4j.pax.logging/milestone/79?closed=1
- 1.10.9:
https://github.com/ops4j/org.ops4j.pax.logging/milestone/81?closed=1
kind regards
Grzegorz Grzybek
[ANN] Pax Logging 2.0.14, 1.11.13 and 1.10.9 released
Posted by Grzegorz Grzybek <gr...@gmail.com>.
Hello
Pax Logging 2.0.14, 1.11.13 and 1.10.9 have been released with two upgrades:
- Log4j2 2.17.1
- Logback 1.2.10
These are the latest versions of the dependencies as of December 30th 2021.
Additionally, 2.0.14 and 1.11.13 contain new configuration property:
"org.ops4j.pax.logging.syncJULFormatter" (defaults to "true") which
controls the usage of `java.util.logging.SimpleFormatter` inside Pax
Logging's JUL Handler. By default, there's a single formatter with
synchronization. When this property is set to "false", new instance is
created for each event being handled - this is special system/context
property to be used in Payara server where some deadlocks were observed.
The changelogs are:
- 2.0.14:
https://github.com/ops4j/org.ops4j.pax.logging/milestone/78?closed=1
- 1.11.13:
https://github.com/ops4j/org.ops4j.pax.logging/milestone/79?closed=1
- 1.10.9:
https://github.com/ops4j/org.ops4j.pax.logging/milestone/81?closed=1
kind regards
Grzegorz Grzybek