dependabot[bot] opened a new pull request, #46:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/46
Bumps
[com.fasterxml.jackson:jackson-bom](https://github.com/FasterXML/jackson-bom)
from 2.16.2 to 2.17.1.
Commits
https://github.com/FasterXML/jackson-bom/commit/
dependabot[bot] commented on PR #42:
URL:
https://github.com/apache/logging-log4j-audit-sample/pull/42#issuecomment-2095802980
Superseded by #46.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
dependabot[bot] closed pull request #42: Bump com.fasterxml.jackson:jackson-bom
from 2.16.2 to 2.17.0
URL: https://github.com/apache/logging-log4j-audit-sample/pull/42
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
github-actions[bot] merged PR #46:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/46
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: not
github-actions[bot] merged PR #46:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/46
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: not
marcreichman-pfi commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2096127506
@ppkarwasz I have a couple new findings, which may make sense to you, but at
the very least I'll try a new configuration and see how it goes. I was able to
dig in a
rm5248 commented on PR #381:
URL: https://github.com/apache/logging-log4cxx/pull/381#issuecomment-2096202951
The updates make me think that maybe we should have a CI action that builds
with the events at exit feature configured to be on to make sure it all builds.
--
This is an automated
dependabot[bot] opened a new pull request, #142:
URL: https://github.com/apache/logging-log4j-audit/pull/142
Bumps
[org.apache.maven.plugin-tools:maven-plugin-tools-api](https://github.com/apache/maven-plugin-tools)
from 3.11.0 to 3.13.0.
Release notes
Sourced from https://github.
dependabot[bot] commented on PR #135:
URL:
https://github.com/apache/logging-log4j-audit/pull/135#issuecomment-2096465485
Superseded by #142.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
dependabot[bot] closed pull request #135: Bump
org.apache.maven.plugin-tools:maven-plugin-tools-api from 3.11.0 to 3.12.0
URL: https://github.com/apache/logging-log4j-audit/pull/135
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
dependabot[bot] commented on PR #136:
URL:
https://github.com/apache/logging-log4j-audit/pull/136#issuecomment-2096469649
Superseded by #143.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
dependabot[bot] closed pull request #136: Bump
org.apache.maven.plugin-tools:maven-plugin-annotations from 3.11.0 to 3.12.0
URL: https://github.com/apache/logging-log4j-audit/pull/136
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitH
dependabot[bot] opened a new pull request, #143:
URL: https://github.com/apache/logging-log4j-audit/pull/143
Bumps
[org.apache.maven.plugin-tools:maven-plugin-annotations](https://github.com/apache/maven-plugin-tools)
from 3.11.0 to 3.13.0.
Release notes
Sourced from https://githu
ppkarwasz commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2096782770
I really ought to look deeper into GlassFish.
The `log4j-jakarta-web` should not create a new logger context **unless**
the classloader returned by `ServletContext#ge
marcreichman-pfi commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2096837528
It does look similar. I think with the changes I mentioned i am actually all
set. I don’t see the warnings on successful rolling that a file is already
open, and I d
marcreichman-pfi closed issue #2566: When logging from multiple threads, an
appender can be broken until app restart if it rolls over
URL: https://github.com/apache/logging-log4j2/issues/2566
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
swebb2066 commented on PR #381:
URL: https://github.com/apache/logging-log4cxx/pull/381#issuecomment-2097162272
Also need a test case for telnetappender and socketappender
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
vy commented on PR #118:
URL:
https://github.com/apache/logging-log4j-tools/pull/118#issuecomment-2097756073
@dependabot rebase
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comme
github-actions[bot] merged PR #118:
URL: https://github.com/apache/logging-log4j-tools/pull/118
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifica
vy opened a new pull request, #120:
URL: https://github.com/apache/logging-log4j-tools/pull/120
This change fixes #117, which misses `loggers > logger` entry.
### Why is the entry missing?
`log4j-core-plugins.xml` contains two entries for `LoggerConfig`:
1. ``
2. ``
ppkarwasz commented on code in PR #120:
URL:
https://github.com/apache/logging-log4j-tools/pull/120#discussion_r1592068351
##
log4j-docgen/src/main/java/org/apache/logging/log4j/docgen/generator/internal/TypeLookup.java:
##
@@ -42,18 +44,106 @@ private TypeLookup(final Iterable
github-actions[bot] merged PR #176:
URL: https://github.com/apache/logging-parent/pull/176
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications
lukasalexanderweber commented on issue #2331:
URL:
https://github.com/apache/logging-log4j2/issues/2331#issuecomment-2098222865
@rgoers the PR you mentioned is merged, is this issue resolved?
--
This is an automated message from the Apache Git Service.
To respond to the message, please lo
vy commented on code in PR #120:
URL:
https://github.com/apache/logging-log4j-tools/pull/120#discussion_r1592413854
##
log4j-docgen/src/main/java/org/apache/logging/log4j/docgen/generator/internal/TypeLookup.java:
##
@@ -42,18 +44,106 @@ private TypeLookup(final Iterable
plugi
vy merged PR #120:
URL: https://github.com/apache/logging-log4j-tools/pull/120
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...
vy closed issue #117: Log4j XSD doesn't define `loggers > logger` element
URL: https://github.com/apache/logging-log4j-tools/issues/117
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific co
rgoers commented on issue #2331:
URL:
https://github.com/apache/logging-log4j2/issues/2331#issuecomment-2098600215
We have not released 2.24.0 yet. You can try with the latest SNAPSHOT
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
swebb2066 merged PR #381:
URL: https://github.com/apache/logging-log4cxx/pull/381
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr
swebb2066 opened a new pull request, #382:
URL: https://github.com/apache/logging-log4cxx/pull/382
Sending just the log message seems a reasonable default when a layout is not
specified in the configuration. Currently Log4cxx causes abnormal termination
in this case.
Also, the number
github-actions[bot] merged PR #134:
URL: https://github.com/apache/logging-log4j-samples/pull/134
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifi
rm5248 commented on code in PR #382:
URL: https://github.com/apache/logging-log4cxx/pull/382#discussion_r1593299310
##
src/main/include/log4cxx/net/telnetappender.h:
##
@@ -80,12 +61,9 @@ class LOG4CXX_EXPORT TelnetAppender : public AppenderSkeleton
~TelnetAppend
swebb2066 opened a new pull request, #383:
URL: https://github.com/apache/logging-log4cxx/pull/383

--
This is an automated message from the Apache Git Service.
To respond to the me
swebb2066 commented on PR #383:
URL: https://github.com/apache/logging-log4cxx/pull/383#issuecomment-2099865449
The [1.3.0 staging web
site](https://logging.staged.apache.org/log4cxx/1.3.0) is available for review.
--
This is an automated message from the Apache Git Service.
To respond to
vy opened a new pull request, #121:
URL: https://github.com/apache/logging-log4j-tools/pull/121
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
ppkarwasz commented on code in PR #121:
URL:
https://github.com/apache/logging-log4j-tools/pull/121#discussion_r1593592657
##
log4j-docgen-maven-plugin/src/main/java/org/apache/logging/log4j/docgen/maven/SchemaGeneratorMojo.java:
##
@@ -50,6 +50,9 @@ public class SchemaGenerato
vy commented on code in PR #121:
URL:
https://github.com/apache/logging-log4j-tools/pull/121#discussion_r1593610182
##
log4j-docgen-maven-plugin/src/main/java/org/apache/logging/log4j/docgen/maven/SchemaGeneratorMojo.java:
##
@@ -50,6 +50,9 @@ public class SchemaGeneratorMojo e
vy merged PR #121:
URL: https://github.com/apache/logging-log4j-tools/pull/121
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...
vy commented on issue #2509:
URL:
https://github.com/apache/logging-log4j2/issues/2509#issuecomment-2100302404
Superseded by #2535.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific c
vy closed issue #2509: Create a `Using a logging API` guide
URL: https://github.com/apache/logging-log4j2/issues/2509
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubsc
ppkarwasz commented on PR #2570:
URL: https://github.com/apache/logging-log4j2/pull/2570#issuecomment-2100433285
@dependabot rebase
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific co
vy opened a new pull request, #122:
URL: https://github.com/apache/logging-log4j-tools/pull/122
Adds support for multiple templates in the
`log4j-docgen:generate-documentation` configuration. In the presence of
multiple templates, some templates might decide to not generate content
conditi
github-actions[bot] merged PR #2570:
URL: https://github.com/apache/logging-log4j2/pull/2570
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notificatio
ppkarwasz commented on code in PR #122:
URL:
https://github.com/apache/logging-log4j-tools/pull/122#discussion_r1593970115
##
log4j-tools-internal-freemarker-util/src/main/java/org/apache/logging/log4j/tools/internal/freemarker/util/FreeMarkerUtils.java:
##
@@ -63,28 +112,39 @@
vy commented on code in PR #122:
URL:
https://github.com/apache/logging-log4j-tools/pull/122#discussion_r1593990802
##
log4j-tools-internal-freemarker-util/src/main/java/org/apache/logging/log4j/tools/internal/freemarker/util/FreeMarkerUtils.java:
##
@@ -63,28 +112,39 @@ privat
vy merged PR #122:
URL: https://github.com/apache/logging-log4j-tools/pull/122
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...
vy commented on issue #111:
URL:
https://github.com/apache/logging-log4j-tools/issues/111#issuecomment-2100558097
Fixed in #121.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comm
vy closed issue #111: Introduce `skip` parameter
URL: https://github.com/apache/logging-log4j-tools/issues/111
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e
github-actions[bot] merged PR #2568:
URL: https://github.com/apache/logging-log4j2/pull/2568
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notificatio
github-actions[bot] merged PR #135:
URL: https://github.com/apache/logging-log4j-samples/pull/135
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifi
github-actions[bot] closed issue #2167: %d{UNIX_MILLIS} is printing 0 as
timestamp in log file
URL: https://github.com/apache/logging-log4j2/issues/2167
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
github-actions[bot] commented on issue #2010:
URL:
https://github.com/apache/logging-log4j2/issues/2010#issuecomment-2101781616
This issue is stale because it has been waiting for your feedback for more
than 60 days. The Apache Logging Services community values every submitted
issue, but w
github-actions[bot] closed issue #1283: Hide PosixViewAttribute related error
info in Windows
URL: https://github.com/apache/logging-log4j2/issues/1283
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go t
github-actions[bot] commented on issue #1804:
URL:
https://github.com/apache/logging-log4j2/issues/1804#issuecomment-2101781644
This issue is stale because it has been waiting for your feedback for more
than 60 days. The Apache Logging Services community values every submitted
issue, but w
swebb2066 merged PR #382:
URL: https://github.com/apache/logging-log4cxx/pull/382
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr
ppkarwasz commented on issue #2010:
URL:
https://github.com/apache/logging-log4j2/issues/2010#issuecomment-2101945761
There must be a bug in the Github Stale action. I'll check it out.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
YahuiWong opened a new issue, #147:
URL: https://github.com/apache/logging-log4net/issues/147
when I publish my dotnet 8 project by aot mode .
then soft can`t working . and have the err msg
```
log4net:ERROR Exception while reading ConfigurationSettings. Check your
.config file is
FreeAndNil commented on issue #147:
URL:
https://github.com/apache/logging-log4net/issues/147#issuecomment-2102164186
@YahuiWong please See #142
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to t
YahuiWong commented on issue #147:
URL:
https://github.com/apache/logging-log4net/issues/147#issuecomment-2102327127
> @YahuiWong please See #142
Is https://github.com/apache/logging-log4net/issues/142 have a solution?
--
This is an automated message from the Apache Git Servic
github-actions[bot] merged PR #177:
URL: https://github.com/apache/logging-parent/pull/177
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications
FreeAndNil commented on issue #147:
URL:
https://github.com/apache/logging-log4net/issues/147#issuecomment-2102431940
@YahuiWong yes, see my comments and #143
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
ppkarwasz opened a new pull request, #123:
URL: https://github.com/apache/logging-log4j-tools/pull/123
We add support for the
[@PluginValue](https://logging.apache.org/log4j/2.x/javadoc/log4j-core/org/apache/logging/log4j/core/config/plugins/PluginValue.html)
annotation.
--
Th
ppkarwasz merged PR #123:
URL: https://github.com/apache/logging-log4j-tools/pull/123
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsu
github-actions[bot] merged PR #54:
URL: https://github.com/apache/logging-log4j-scala/pull/54
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notificati
github-actions[bot] merged PR #178:
URL: https://github.com/apache/logging-parent/pull/178
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications
github-actions[bot] merged PR #2573:
URL: https://github.com/apache/logging-log4j2/pull/2573
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notificatio
hordi commented on issue #373:
URL:
https://github.com/apache/logging-log4cxx/issues/373#issuecomment-2104701140
Finally have found how to turn off TBB thread - do not getting the crash in
run log4cxx shutdown any more.
--
This is an automated message from the Apache Git Service.
To resp
grobmeier commented on issue #2507:
URL:
https://github.com/apache/logging-log4j2/issues/2507#issuecomment-2104715332
Added some changes with:
85c61ca6e1ecce697697dbc3f62745f4d0e03d03
e6ef19f902483734f93b66d93b9532505e15cec1
69169e6176f83b7c199639c5635816ead4ce9a7a
e6ef19f9024837
swebb2066 commented on issue #373:
URL:
https://github.com/apache/logging-log4cxx/issues/373#issuecomment-2105409263
@hordi Thank you for the update
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
swebb2066 merged PR #383:
URL: https://github.com/apache/logging-log4cxx/pull/383
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr
ppkarwasz opened a new pull request, #2574:
URL: https://github.com/apache/logging-log4j2/pull/2574
Closes #2525
This PR provides an almost complete rewrite of the current [Configuration
page](https://logging.apache.org/log4j/2.x/manual/configuration.html), based on
these principles
FreeAndNil commented on issue #142:
URL:
https://github.com/apache/logging-log4net/issues/142#issuecomment-2106367905
@SwEngine could you take a look?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to g
sullis opened a new pull request, #136:
URL: https://github.com/apache/logging-log4j-samples/pull/136
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubs
swebb2066 closed issue #373: Delay/pause/crash in LogManager::shutdown()
URL: https://github.com/apache/logging-log4cxx/issues/373
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment
ppkarwasz commented on issue #1539:
URL:
https://github.com/apache/logging-log4j2/issues/1539#issuecomment-2106766878
This is partially solved in #2392: this PR eliminates the usage of Java 8
features not supported by GraalVM.
After the release of `2.24.0` users will be able to use G
vy commented on PR #136:
URL:
https://github.com/apache/logging-log4j-samples/pull/136#issuecomment-2106781982
@sullis, could you remove [this dependabot ignore
rule](https://github.com/apache/logging-log4j-samples/blob/44c3348906d2d160e6affd152e63eaa0c0554d76/.github/dependabot.yaml#L49)
sullis commented on PR #136:
URL:
https://github.com/apache/logging-log4j-samples/pull/136#issuecomment-2107523029
> @sullis, could you remove [this dependabot ignore
rule](https://github.com/apache/logging-log4j-samples/blob/44c3348906d2d160e6affd152e63eaa0c0554d76/.github/dependabot.yaml#
vy commented on PR #136:
URL:
https://github.com/apache/logging-log4j-samples/pull/136#issuecomment-2107573938
@sullis, you need to sign your commits too:
```
git reset HEAD~2
git commit -a -S -m 'Upgrade LMAX Disruptor to version 4.0.0 (#136)'
git push -f origin
```
--
ppkarwasz commented on issue #2025:
URL:
https://github.com/apache/logging-log4j2/issues/2025#issuecomment-2108131274
Actually there is another usage of `immediateFlush`: resource managers use a
`ByteBuffer` to format each log event.
If `immediateFlush` is `true`, the byte buffer is
ppkarwasz commented on issue #2528:
URL:
https://github.com/apache/logging-log4j2/issues/2528#issuecomment-2108162517
While restructuring the "Appenders" page we should explain the meaning of
the `immediateFlush` option.
Looking at #2023, #2025 and other discussions, users often think th
sullis commented on PR #136:
URL:
https://github.com/apache/logging-log4j-samples/pull/136#issuecomment-2108169629
Force pushed my latest update.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
vy commented on PR #136:
URL:
https://github.com/apache/logging-log4j-samples/pull/136#issuecomment-2108312362
@sullis, I think you used `-s` instead of `-S` I shared. I cannot see commit
signatures, but a sign-off comment.
(Sorry for the trouble. As you know, I could have implemente
vy commented on code in PR #2574:
URL: https://github.com/apache/logging-log4j2/pull/2574#discussion_r1598823140
##
src/site/antora/modules/ROOT/pages/manual/configuration.adoc:
##
@@ -14,1856 +14,1024 @@
See the License for the specific language governing permissions and
vy commented on code in PR #2574:
URL: https://github.com/apache/logging-log4j2/pull/2574#discussion_r1598823140
##
src/site/antora/modules/ROOT/pages/manual/configuration.adoc:
##
@@ -14,1856 +14,1024 @@
See the License for the specific language governing permissions and
sullis commented on PR #136:
URL:
https://github.com/apache/logging-log4j-samples/pull/136#issuecomment-2108439592
I just pushed another update.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
vy merged PR #136:
URL: https://github.com/apache/logging-log4j-samples/pull/136
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr.
grobmeier commented on code in PR #2574:
URL: https://github.com/apache/logging-log4j2/pull/2574#discussion_r1598987120
##
src/site/antora/modules/ROOT/pages/manual/filters.adoc:
##
@@ -14,32 +14,77 @@
See the License for the specific language governing permissions and
github-actions[bot] merged PR #28:
URL: https://github.com/apache/logging-log4j-jakarta/pull/28
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifica
vy opened a new pull request, #2576:
URL: https://github.com/apache/logging-log4j2/pull/2576
Fixes #2533.
Reviewers are recommended to checkout the branch locally, build, and view it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
vy commented on code in PR #2574:
URL: https://github.com/apache/logging-log4j2/pull/2574#discussion_r1599864587
##
src/site/antora/modules/ROOT/pages/manual/configuration.adoc:
##
@@ -14,1856 +14,1024 @@
See the License for the specific language governing permissions and
pjfanning commented on PR #46:
URL:
https://github.com/apache/logging-log4j-scala/pull/46#issuecomment-2110141625
@vy this is not an LTS release. Could you revert this? If you build a jar
with Scala 3.4.x, it will only work with 3.4.x - and therefore the jar will not
work with any LTS vers
pjfanning commented on PR #46:
URL:
https://github.com/apache/logging-log4j-scala/pull/46#issuecomment-2110149513
I have a question. I thought it was an ASF requirement for humans to be
involved in commits. This PR was generated by a bot and merged by a bot with no
apparent human input. Am
vy closed issue #55: Scala 3.4.x is not an LTS release and compiling with it
means you don't support Scala 3.3 (the latest LTS releases)
URL: https://github.com/apache/logging-log4j-scala/issues/55
--
This is an automated message from the Apache Git Service.
To respond to the message, please
vy commented on issue #55:
URL:
https://github.com/apache/logging-log4j-scala/issues/55#issuecomment-2110160009
@pjfanning, I will handle this promptly. Give me a sec.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use t
vy commented on PR #46:
URL:
https://github.com/apache/logging-log4j-scala/pull/46#issuecomment-2110202578
@pjfanning, thanks so much for the heads up. I have fixed the issue in
15bf38f1fc7159b58f4759466b26c2d270ab8b08. This PR _unintentionally_ slipped
through in February due to a `depend
ppkarwasz opened a new pull request, #2577:
URL: https://github.com/apache/logging-log4j2/pull/2577
We refresh the asynchronous logging page by:
* marking more clearly that _asynchronous logging_ is not the solution to
all performance problems. Depending on the case it could give
rgoers commented on PR #46:
URL:
https://github.com/apache/logging-log4j-scala/pull/46#issuecomment-2110352679
@vy Did I miss something? I don't recall a vote where the project agreed to
let dependabot apply updates automatically. I certainly never voted to make
dependabot a committer.
-
vy commented on PR #46:
URL:
https://github.com/apache/logging-log4j-scala/pull/46#issuecomment-2110377693
@rgoers, are you seriously asking this or there is a pun intended?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
ppkarwasz commented on code in PR #2574:
URL: https://github.com/apache/logging-log4j2/pull/2574#discussion_r1600139016
##
src/site/antora/modules/ROOT/examples/configuration/filters.xml:
##
@@ -0,0 +1,40 @@
+
+
+https://logging.apache.org/xml/ns";
+ xmlns:xsi="htt
ppkarwasz commented on code in PR #2574:
URL: https://github.com/apache/logging-log4j2/pull/2574#discussion_r1600155990
##
src/site/antora/modules/ROOT/nav.adoc:
##
@@ -40,20 +40,23 @@
** xref:manual/thread-context.adoc[]
** xref:manual/scoped-context.adoc[]
** xref:manual/re
ppkarwasz commented on code in PR #2574:
URL: https://github.com/apache/logging-log4j2/pull/2574#discussion_r1600163337
##
src/site/antora/modules/ROOT/pages/manual/appenders.adoc:
##
@@ -466,8 +466,8 @@ A Failover configuration might look like:
-[#FileAppender]
-== Fi
1201 - 1300 of 14008 matches
Mail list logo