jaykataria commented on PR #3265:
URL: https://github.com/apache/logging-log4j2/pull/3265#issuecomment-2574440671
@ppkarwasz I have rebased the commit, let me know if anything else is needed
on this or we can close this out. Thanks for this!
--
This is an automated message from the Ap
jaykataria commented on PR #3265:
URL: https://github.com/apache/logging-log4j2/pull/3265#issuecomment-2574416661
@ppkarwasz , this one is still open I will rebase this just for tracking
purposes, I do not recall any action items on this would you remember?
--
This is an automated me
jaykataria commented on PR #3217:
URL: https://github.com/apache/logging-log4j2/pull/3217#issuecomment-2574412773
Thanks @ppkarwasz , for the answers, let me make a PR soon :) finally got
back from vacation :)
--
This is an automated message from the Apache Git Service.
To respond to
JWT007 commented on issue #3368:
URL:
https://github.com/apache/logging-log4j2/issues/3368#issuecomment-2573834639
I am surprised to hear that these should *never* be accessed
programmatically?
We have been doing this for years to create dynamic runtime-only appenders
and loggers -
github-actions[bot] merged PR #157:
URL: https://github.com/apache/logging-log4j-transform/pull/157
--
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: noti
vy commented on issue #3368:
URL:
https://github.com/apache/logging-log4j2/issues/3368#issuecomment-2573789575
I would expect there to be more compatibility implications. Nevertheless,
these classes should never be accessed programmatically — that is how we
advise users in docs too. He
ppkarwasz commented on PR #3367:
URL: https://github.com/apache/logging-log4j2/pull/3367#issuecomment-2573775500
> (KO’ed by flu. Responding from bed.)
Get better soon!
>Changes LGTM. I think we should later move the site from root to a leaf
module. This might help us to implem
ppkarwasz merged PR #3367:
URL: https://github.com/apache/logging-log4j2/pull/3367
--
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
vy commented on PR #3367:
URL: https://github.com/apache/logging-log4j2/pull/3367#issuecomment-2573743549
(KO’ed by flu. Responding from bed.)
Changes LGTM. I think we should later move the site from root to a leaf
module. This might help us to implement “site should run after all
github-actions[bot] merged PR #3305:
URL: https://github.com/apache/logging-log4j2/pull/3305
--
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 merged PR #3365:
URL: https://github.com/apache/logging-log4j2/pull/3365
--
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
github-actions[bot] merged PR #3346:
URL: https://github.com/apache/logging-log4j2/pull/3346
--
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 #3363:
URL: https://github.com/apache/logging-log4j2/pull/3363
--
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 issue #3368:
URL:
https://github.com/apache/logging-log4j2/issues/3368#issuecomment-2573315201
> From a coding perspective a trivial change but more of a binary
compatibility problem.
Removing the type variable `B` should be binary compatible (the erasure of
`
github-actions[bot] merged PR #3362:
URL: https://github.com/apache/logging-log4j2/pull/3362
--
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
ranger2025 commented on issue #3357:
URL:
https://github.com/apache/logging-log4j2/issues/3357#issuecomment-2573298257
@ppkarwasz,
Thank you very much for your help. I've understood how to get module name.
About layers. I have a multi layer program where every layer is a subsy
ppkarwasz closed pull request #3344: Bump org.json:json from 20240303 to
20241224
URL: https://github.com/apache/logging-log4j2/pull/3344
--
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
ppkarwasz closed pull request #3364: Bump org.assertj:assertj-core from 3.26.3
to 3.27.2
URL: https://github.com/apache/logging-log4j2/pull/3364
--
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 s
ppkarwasz closed pull request #3324: Bump com.code-intelligence:jazzer from
0.22.1 to 0.23.0
URL: https://github.com/apache/logging-log4j2/pull/3324
--
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
ppkarwasz commented on PR #3326:
URL: https://github.com/apache/logging-log4j2/pull/3326#issuecomment-2573277324
@vy,
Could you check this one? It appears there is a breaking change in the
library.
--
This is an automated message from the Apache Git Service.
To respond to the messa
Philippe Cloutier created LOG4J2-3695:
-
Summary: Release Notes table of contents is partial (first level
only)
Key: LOG4J2-3695
URL: https://issues.apache.org/jira/browse/LOG4J2-3695
Project: Log4
JWT007 opened a new issue, #3368:
URL: https://github.com/apache/logging-log4j2/issues/3368
**Log4j 2.24**
_Not technically a bug??? But not a feature-request either...just pointing
it out...if no interest in changing this from L4J team go ahead and close it_
The appender Buil
ppkarwasz opened a new pull request, #3367:
URL: https://github.com/apache/logging-log4j2/pull/3367
Since Dependabot cannot handle multiple versions of the same artifact at
once, our Dependabot configuration for `2.x` is split into two runs:
- One Dependabot run handles the dependency
ppkarwasz commented on issue #3257:
URL:
https://github.com/apache/logging-log4j2/issues/3257#issuecomment-2573165646
@eldwrjwt,
Thanks for the PRs. Your fixes have been included in the latest
`2.25.0-SNAPSHOT`.
See the [download page](https://logging.apache.org/download.html) for
darkSheep404 commented on issue #3358:
URL:
https://github.com/apache/logging-log4j2/issues/3358#issuecomment-2573085556
got it , many thx
--
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 spe
darkSheep404 closed issue #3358: Log4j2 yml config do not support YAML Anchors
and Aliases
URL: https://github.com/apache/logging-log4j2/issues/3358
--
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
[
https://issues.apache.org/jira/browse/LOG4J2-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz reassigned LOG4J2-2750:
-
Assignee: Piotr Karwasz
> Setting to disable extended stack trace for layouts
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz reassigned LOG4J2-2750:
-
Assignee: Volkan Yazici (was: Piotr Karwasz)
> Setting to disable extended stack trace
[
https://issues.apache.org/jira/browse/LOG4J2-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-3453.
---
Resolution: Fixed
This issue is now followed on GitHub:
https://github.com/apache/logging-l
[
https://issues.apache.org/jira/browse/LOG4J2-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz reassigned LOG4J2-2632:
-
Assignee: Volkan Yazici (was: Piotr Karwasz)
> Package filter not working with %ex con
[
https://issues.apache.org/jira/browse/LOG4J2-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910200#comment-17910200
]
Piotr Karwasz commented on LOG4J2-2632:
---
[~vy],
Is this fixed now? Can you mark i
[
https://issues.apache.org/jira/browse/LOG4J2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-3662.
---
Fix Version/s: 2.24.0
Resolution: Fixed
This was fixed in {{2.24.0}}: see release not
[
https://issues.apache.org/jira/browse/LOG4J2-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-3651.
---
Resolution: Fixed
The problem does not occur in the new documentation:
https://logging.apac
[
https://issues.apache.org/jira/browse/LOG4J2-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910181#comment-17910181
]
Piotr Karwasz commented on LOG4J2-2750:
---
[~vy],
Is this resolved?
> Setting to d
[
https://issues.apache.org/jira/browse/LOG4J2-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-3581.
---
Resolution: Fixed
Source migration has been solved using OpenRewrite in:
* https://github.c
[
https://issues.apache.org/jira/browse/LOG4J2-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-3624.
---
Fix Version/s: 2.23.0
Resolution: Fixed
{{StatusLogger}} has been rewritten in versio
[
https://issues.apache.org/jira/browse/LOG4J2-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-3554.
---
Fix Version/s: 2.20.0
Resolution: Fixed
> Replace old com.sun.mail:smtp with org.ecli
[
https://issues.apache.org/jira/browse/LOG4J2-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-3510.
---
Resolution: Fixed
I am closing this, since the documentation website has been entirely rewri
ppkarwasz merged PR #3260:
URL: https://github.com/apache/logging-log4j2/pull/3260
--
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 issue #3257: File line numbers are not printed for the
failover appender when using AsyncLoggerContextSelector
URL: https://github.com/apache/logging-log4j2/issues/3257
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Gi
ppkarwasz merged PR #3259:
URL: https://github.com/apache/logging-log4j2/pull/3259
--
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 commented on issue #3357:
URL:
https://github.com/apache/logging-log4j2/issues/3357#issuecomment-2572950037
@ranger2025,
### Filtering by module name
To filter by module name you can use the existing
[`ScriptFilter`](https://logging.apache.org/log4j/2.x/manual/filter
ppkarwasz commented on issue #3358:
URL:
https://github.com/apache/logging-log4j2/issues/3358#issuecomment-2572901859
The YAML features that you can use in a Log4j configuration depend on the
features supported by the parser we use.
Since the [Jackson YAML data format
module](https://gi
github-actions[bot] merged PR #3361:
URL: https://github.com/apache/logging-log4j2/pull/3361
--
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
[
https://issues.apache.org/jira/browse/LOG4J2-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Thomas closed LOG4J2-3665.
---
Resolution: Won't Fix
> Dynamically created loggers do not respect "Named Hierarchy"
> -
[
https://issues.apache.org/jira/browse/LOG4J2-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910090#comment-17910090
]
Jeff Thomas commented on LOG4J2-3665:
-
Closing old issues created by me in old issue
[
https://issues.apache.org/jira/browse/LOG4J2-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Thomas closed LOG4J2-3664.
---
Resolution: Won't Fix
Not duplicated in GitHub - in the meantime I personally have found a different
[
https://issues.apache.org/jira/browse/LOG4J2-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Thomas closed LOG4J2-3632.
---
Resolution: Feedback Received
> Using log4j-1_2-api to load XML configuration - Logger.getAppenders(
[
https://issues.apache.org/jira/browse/LOG4J2-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Thomas closed LOG4J2-3690.
---
Resolution: Duplicate
> Small documentation error - RollingFile Appenders - 'createOnDemand' attribu
[
https://issues.apache.org/jira/browse/LOG4J2-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Thomas closed LOG4J2-3691.
---
Resolution: Feedback Received
> Documentation: CompositeTriggeringPolicy - nested element?
> --
[
https://issues.apache.org/jira/browse/LOG4J2-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910084#comment-17910084
]
Jeff Thomas commented on LOG4J2-3693:
-
GitHub issue created - [https://github.com/ap
[
https://issues.apache.org/jira/browse/LOG4J2-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Thomas closed LOG4J2-3693.
---
Resolution: Duplicate
> XmlConfiguration keeps relevant fields private without providing protected
JWT007 opened a new issue, #3360:
URL: https://github.com/apache/logging-log4j2/issues/3360
**Log4j 2.24**
The XmlConfiguration implementation is non-final meaning it is possible to
subclass it to provide additional custom functionality; however: the most
relevant class field `rootEl
[
https://issues.apache.org/jira/browse/LOG4J2-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910083#comment-17910083
]
Jeff Thomas commented on LOG4J2-3694:
-
Moved to Github - [https://github.com/apache/
[
https://issues.apache.org/jira/browse/LOG4J2-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Thomas closed LOG4J2-3694.
---
Resolution: Duplicate
> Javadoc: TypeConverters convert for "Level" incorrectly documents behaviour
JWT007 opened a new issue, #3359:
URL: https://github.com/apache/logging-log4j2/issues/3359
Minor Javadoc correction.
In **TypeConverters**, the conversion for type "Level" says it returns
'null' for invalid levels:
```
/**
* Converts a {@link String} into a Log4j {@link
[
https://issues.apache.org/jira/browse/LOG4J2-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910080#comment-17910080
]
Jeff Thomas commented on LOG4J2-3694:
-
[~pkarwasz] - Facepalm... sorrry just went wi
darkSheep404 opened a new issue, #3358:
URL: https://github.com/apache/logging-log4j2/issues/3358
## Description
Log4j2 yml config do not support YAML Anchors and Aliases with error Logger
contains an invalid element or attribute "<<"
```
Configuration:
status: WARN
Ap
[
https://issues.apache.org/jira/browse/LOG4J2-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910054#comment-17910054
]
Piotr Karwasz commented on LOG4J2-3694:
---
[~JWT007],
Please open a [GitHub issue|h
[
https://issues.apache.org/jira/browse/LOG4J2-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910053#comment-17910053
]
Piotr Karwasz commented on LOG4J2-3693:
---
[~JWT007],
Please open a [GitHub issue|h
60 matches
Mail list logo
