ctubbsii commented on issue #3100:
URL:
https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2794252378
@ppkarwasz wrote:
> That is easy to explain: I increased the level of those lifecycle messages
in [#3043](https://github.com/apache/logging-log4j2/pull/3043) to make t
ctubbsii commented on PR #3043:
URL: https://github.com/apache/logging-log4j2/pull/3043#issuecomment-2794256152
These changes made the status logger much more noisy at the INFO level. The
extra lifecycle messages should be at the DEBUG level instead. See
https://github.com/apache/logging-lo
ppkarwasz commented on code in PR #279:
URL:
https://github.com/apache/logging-log4j-samples/pull/279#discussion_r2037015235
##
.github/workflows/gradle-reusable-test.yaml:
##
@@ -64,6 +64,17 @@ jobs:
develocity-url: https://develocity.apache.org
develocit
ppkarwasz merged PR #279:
URL: https://github.com/apache/logging-log4j-samples/pull/279
--
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-un
ppkarwasz commented on PR #3582:
URL: https://github.com/apache/logging-log4j2/pull/3582#issuecomment-2792077977
I modified this PR according to the [vote on
`dev@logging`](https://lists.apache.org/thread/8ffdw1zqrvwrsdr0ng0m2rgtdnpzg4hk).
Can you check if the values look good to you?
ppkarwasz opened a new issue, #178:
URL: https://github.com/apache/logging-log4j-tools/issues/178
The `profile` property of the `publish` element in `.asf.yaml` is not
supported and should be removed from the `deploy-site.yaml` workflow.
--
This is an automated message from the Apache Git
ppkarwasz opened a new issue, #3599:
URL: https://github.com/apache/logging-log4j2/issues/3599
## Description
PR #2941 introduces some basic logging of the most important `Configuration`
lifecycle events at an `INFO` level. The messages are meant to convey:
- which configuratio
vy commented on PR #367:
URL: https://github.com/apache/logging-parent/pull/367#issuecomment-2784482041
@ppkarwasz, mind sharing the motivation for this feature, please? I mean,
what do we fix? If we don't fix anything, but improve something, what is that
we improve and why do we want this
ppkarwasz commented on PR #279:
URL:
https://github.com/apache/logging-log4j-samples/pull/279#issuecomment-2794939224
Some additional changes were required post merge:
- 985500982ed2ebb97078869abd8bf34d0b762189
- ba0f4357bc5819577288ec90f9ca7c4499123065
- f3673118d374da6f46af607
ppkarwasz opened a new pull request, #313:
URL: https://github.com/apache/logging-log4j-samples/pull/313
This PR:
- Limits the usage of `repository.apache.org` to artifacts in the
`org.apache.logging` group.
- Uses the Snapshots repository only if `log4j.repository.url` is not
spe
ppkarwasz opened a new issue, #373:
URL: https://github.com/apache/logging-parent/issues/373
As documented on the [ASF Parent POM
website](https://maven.apache.org/pom/asf/), since version `34` the ASF Parent
POM moves the `apache.snapshots` repository to the `use-apache-snapshots`
profile
jjohannes commented on code in PR #279:
URL:
https://github.com/apache/logging-log4j-samples/pull/279#discussion_r2037188795
##
.github/workflows/gradle-reusable-test.yaml:
##
@@ -64,6 +64,17 @@ jobs:
develocity-url: https://develocity.apache.org
develocit
vy opened a new issue, #374:
URL: https://github.com/apache/logging-parent/issues/374
`publish.profile: ~` is [not
supported](https://the-asf.slack.com/archives/CBX4TSBQ8/p1744134668222539) by
[`.asf.yaml`](/apache/infrastructure-asfyaml/blob/main/README.md#web-site-deployment-service-for-g
ppkarwasz commented on PR #3450:
URL: https://github.com/apache/logging-log4j2/pull/3450#issuecomment-2795106058
@jjohannes,
The CI build no.
[14389096405](https://github.com/apache/logging-log4j2/actions/runs/14389096405),
which includes the integration tests in `logging-log4j-sampl
ppkarwasz merged PR #3594:
URL: https://github.com/apache/logging-log4j2/pull/3594
--
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-unsubsc
ppkarwasz closed pull request #316: Bump log4j.version from 0.0.0-SNAPSHOT to
3.0.0-beta3
URL: https://github.com/apache/logging-log4j-samples/pull/316
--
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
dependabot[bot] commented on PR #68:
URL:
https://github.com/apache/logging-log4j-audit-sample/pull/68#issuecomment-2789457074
Superseded by #70.
--
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
ppkarwasz closed pull request #300: Bump com.android.library from 8.8.0 to
8.9.1 in /log4j-samples-android
URL: https://github.com/apache/logging-log4j-samples/pull/300
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
ppkarwasz closed pull request #299: Bump com.android.application from 8.8.2 to
8.9.1 in /log4j-samples-android
URL: https://github.com/apache/logging-log4j-samples/pull/299
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
ppkarwasz opened a new pull request, #314:
URL: https://github.com/apache/logging-log4j-samples/pull/314
This PR passes arguments to the Gradle builds via the `LOG4J_VERSION` and
`LOG4J_REPOSITORY_URL` environment variables.
This simplifies the build, since no command line parameters
ctubbsii commented on issue #3100:
URL:
https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2795277686
As purely a user of logging, and not a developer of it, I think I take for
granted that logging will be started through the automatic configuration purely
from the environme
ppkarwasz commented on PR #288:
URL:
https://github.com/apache/logging-log4j-samples/pull/288#issuecomment-2788840502
@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 speci
github-actions[bot] merged PR #371:
URL: https://github.com/apache/logging-parent/pull/371
--
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
ppkarwasz merged PR #308:
URL: https://github.com/apache/logging-log4j-samples/pull/308
--
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-un
ppkarwasz commented on issue #3100:
URL:
https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2795002706
> For me, the INFO level should be reserved for mandatory lifecycle
information that the user should see under normal circumstances. The DEBUG
level should be used for life
ppkarwasz merged PR #3450:
URL: https://github.com/apache/logging-log4j2/pull/3450
--
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-unsubsc
26 matches
Mail list logo
