ppkarwasz commented on issue #1870:
URL:
https://github.com/apache/logging-log4j2/issues/1870#issuecomment-1769925042
@JohnLussmyer,
If you change the `fileIndex` option the problem should solve itself: as
explained above all the `stuff..log.zip` files were originally
swebb2066 merged PR #275:
URL: https://github.com/apache/logging-log4cxx/pull/275
--
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:
swebb2066 merged PR #276:
URL: https://github.com/apache/logging-log4cxx/pull/276
--
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:
swebb2066 opened a new pull request, #276:
URL: https://github.com/apache/logging-log4cxx/pull/276
(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
JohnLussmyer commented on issue #1870:
URL:
https://github.com/apache/logging-log4j2/issues/1870#issuecomment-1769553439
Ahh, thanks. Yet Another option I missed.
Though, the file naming in the .zip files just screws everything up. If you
want to unzip all the logs - you have to
ppkarwasz commented on issue #1870:
URL:
https://github.com/apache/logging-log4j2/issues/1870#issuecomment-1769150702
@JohnLussmyer,
The default configuration of
[`DefaultRolloverStrategy`](https://logging.apache.org/log4j/2.x/manual/appenders.html#rollover-strategies)
keeps only 7
JohnLussmyer commented on issue #1870:
URL:
https://github.com/apache/logging-log4j2/issues/1870#issuecomment-1769129570
One thing I just figured out is that when rolling the logs, it only counts
up to 7.
After that, it starts deleting the oldest log, and renumbering the others.
JohnLussmyer opened a new issue, #1870:
URL: https://github.com/apache/logging-log4j2/issues/1870
## Description
When using a RollingRandomAccessFile appender that zips the logs, and there
are multiple threads really spewing logging, when log4j zip's the previous log
file - it often
ppkarwasz commented on issue #34:
URL: https://github.com/apache/logging-parent/issues/34#issuecomment-1768500486
Sounds more like a bug to me.
I can try to fix it or report it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
vy commented on issue #34:
URL: https://github.com/apache/logging-parent/issues/34#issuecomment-1768457336
Shall we put the `bnd-maven-plugin` under `project > build > plugins` to a
separate profile activated via `bnd.skip` instead? Or does this sound more like
a bug that should be filed
ppkarwasz commented on issue #1865:
URL:
https://github.com/apache/logging-log4j2/issues/1865#issuecomment-1768409301
There are some workarounds:
1. JCL has many ways to configure a `LogFactory` (that is probably why our
tests didn't detect it). For example you can add a
rbri commented on issue #1865:
URL:
https://github.com/apache/logging-log4j2/issues/1865#issuecomment-1768380467
@ppkarwasz wow that was fast, thanks
I guess there is nothing i can do for the moment and i have to wait for
2.22.1 - correct?
--
This is an automated message from the
ppkarwasz commented on issue #1865:
URL:
https://github.com/apache/logging-log4j2/issues/1865#issuecomment-1768373640
@rbri,
The logs you are looking for actually come from the Apache Commons Logging
bridge (`log4j-jcl`). In version `2.21.0` we replaced a manually written
ppkarwasz commented on issue #34:
URL: https://github.com/apache/logging-parent/issues/34#issuecomment-1768335321
This is probably caused by the `true
ppkarwasz commented on issue #1867:
URL:
https://github.com/apache/logging-log4j2/issues/1867#issuecomment-1768223375
> What about japicmp?
I added a list of candidates to the initial comment that we will evaluate in
due time.
In version `2.21.0` I gave
garydgregory commented on issue #1867:
URL:
https://github.com/apache/logging-log4j2/issues/1867#issuecomment-1768145628
What about japicmp?
--
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] commented on PR #48:
URL: https://github.com/apache/logging-parent/pull/48#issuecomment-1768012004
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or minor version,
github-actions[bot] commented on PR #48:
URL: https://github.com/apache/logging-parent/pull/48#issuecomment-1768011878
Changes are applied by CI in 53062eaf3c5ed67bab994bf9e2af251a3701dc99
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
github-actions[bot] closed pull request #48: Bump actions/checkout from 4.1.0
to 4.1.1
URL: https://github.com/apache/logging-parent/pull/48
--
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] opened a new pull request, #48:
URL: https://github.com/apache/logging-parent/pull/48
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.0 to
4.1.1.
Release notes
Sourced from https://github.com/actions/checkout/releases;>actions/checkout's
rbri commented on issue #1865:
URL:
https://github.com/apache/logging-log4j2/issues/1865#issuecomment-1767886643
@ppkarwasz thanks for your fast answer
to reproduce you can do
* get the project - you need jdk 11 to run the tests
* the test is
[
https://issues.apache.org/jira/browse/LOG4J2-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici resolved LOG4J2-3669.
---
Resolution: Fixed
> Update links and license for scala-logging inspired code
>
[
https://issues.apache.org/jira/browse/LOG4J2-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici reassigned LOG4J2-3669:
-
Assignee: Volkan Yazici
> Update links and license for scala-logging inspired code
>
[
https://issues.apache.org/jira/browse/LOG4J2-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776537#comment-17776537
]
Volkan Yazici commented on LOG4J2-3669:
---
[~fanningpj], thanks so much for the heads up. I have
[
https://issues.apache.org/jira/browse/LOG4J2-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici closed LOG4J2-3669.
-
> Update links and license for scala-logging inspired code
>
ppkarwasz commented on issue #1865:
URL:
https://github.com/apache/logging-log4j2/issues/1865#issuecomment-1767874882
@rbri,
I am not aware of any changes in `2.21.0` that could change the way this
code works. Can you pinpoint the unit tests in
ppkarwasz opened a new pull request, #1866:
URL: https://github.com/apache/logging-log4j2/pull/1866
This PR makes the necessary adjustments to port #1819 to the `main` branch.
Except the changes that were already performed in `2.x` it:
* removes explicit `module-info.java`
dependabot[bot] commented on PR #44:
URL: https://github.com/apache/logging-parent/pull/44#issuecomment-1767864369
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or minor version,
github-actions[bot] commented on PR #44:
URL: https://github.com/apache/logging-parent/pull/44#issuecomment-1767864226
Changes are applied by CI in f78e01d80084436ba3c430257cb7ca79489af47f
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
github-actions[bot] closed pull request #44: Bump
com.github.spotbugs:spotbugs-annotations from 4.7.3 to 4.8.0
URL: https://github.com/apache/logging-parent/pull/44
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
vy commented on PR #44:
URL: https://github.com/apache/logging-parent/pull/44#issuecomment-1767856852
@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 comment.
To
github-actions[bot] commented on PR #45:
URL: https://github.com/apache/logging-parent/pull/45#issuecomment-1767854772
Changes are applied by CI in f7fbeee3ceacfe62488fad5943d07cad06ec800d
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
github-actions[bot] closed pull request #45: Bump ossf/scorecard-action from
2.2.0 to 2.3.0
URL: https://github.com/apache/logging-parent/pull/45
--
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] commented on PR #45:
URL: https://github.com/apache/logging-parent/pull/45#issuecomment-1767854919
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or minor version,
vy commented on PR #45:
URL: https://github.com/apache/logging-parent/pull/45#issuecomment-1767840803
@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 comment.
To
dependabot[bot] commented on PR #48:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/48#issuecomment-1767839136
Looks like these dependencies are no longer being updated by Dependabot, so
this is no longer needed.
--
This is an automated message from the Apache Git Service.
To
dependabot[bot] closed pull request #48: Bump kotlin.version from 1.6.21 to
1.9.10
URL: https://github.com/apache/logging-log4j-kotlin/pull/48
--
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
37 matches
Mail list logo
