[
https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112792#comment-17112792
]
Ralph Goers edited comment on LOG4J2-2848 at 5/21/20, 4:36 AM:
---
[
https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112792#comment-17112792
]
Ralph Goers edited comment on LOG4J2-2848 at 5/21/20, 4:26 AM:
---
[
https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112792#comment-17112792
]
Ralph Goers commented on LOG4J2-2848:
-
I believe killing the Mongodb2 module needs t
qoomon commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631819079
thx guys
This is an automated message from the Apache Git Service.
To respond to the message, please lo
[
https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated LOG4J2-2848:
Summary: Create module log4j-mongodb4 to use new major version 4 MongoDB
driver (was: Cre
rocketraman closed pull request #8:
URL: https://github.com/apache/logging-log4j-kotlin/pull/8
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abov
rocketraman commented on pull request #8:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/8#issuecomment-631743569
Rebased and merged to `master`.
This is an automated message from the Apache Git Service.
To respond
[
https://issues.apache.org/jira/browse/LOG4J2-2433?focusedWorklogId=435711&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-435711
]
ASF GitHub Bot logged work on LOG4J2-2433:
--
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/LOG4J2-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112633#comment-17112633
]
ASF subversion and git services commented on LOG4J2-2433:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-2433?focusedWorklogId=435710&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-435710
]
ASF GitHub Bot logged work on LOG4J2-2433:
--
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/LOG4J2-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112632#comment-17112632
]
ASF subversion and git services commented on LOG4J2-2433:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112627#comment-17112627
]
Ralph Goers commented on LOG4J2-2849:
-
The event Lookup was added in 2.13.2. I would
rocketraman merged pull request #11:
URL: https://github.com/apache/logging-log4j-kotlin/pull/11
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
[
https://issues.apache.org/jira/browse/LOG4J2-2843?focusedWorklogId=435707&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-435707
]
ASF GitHub Bot logged work on LOG4J2-2843:
--
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/LOG4J2-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112626#comment-17112626
]
ASF subversion and git services commented on LOG4J2-2843:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-2433?focusedWorklogId=435706&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-435706
]
ASF GitHub Bot logged work on LOG4J2-2433:
--
Author: ASF GitHub Bot
rocketraman commented on pull request #8:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/8#issuecomment-631738478
> I'm curious about the garbage generating behavior of suspending and
resuming the map and stack.
Good question. Probably needs a benchmark. I added JMH in
ht
[
https://issues.apache.org/jira/browse/LOG4J2-2433?focusedWorklogId=435705&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-435705
]
ASF GitHub Bot logged work on LOG4J2-2433:
--
Author: ASF GitHub Bot
rocketraman edited a comment on pull request #8:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/8#issuecomment-631738478
> I'm curious about the garbage generating behavior of suspending and
resuming the map and stack.
Good question. I added JMH in
https://github.com/apac
rocketraman commented on pull request #12:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/12#issuecomment-631728782
@jvz /review please.
This is an automated message from the Apache Git Service.
To respond to the m
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Description:
When I instantiate LocalizedMessageFactory with the String baseName const
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Description:
When I instantiate LocalizedMessageFactory with the String baseName const
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Description:
When I instantiate LocalizedMessageFactory with the String baseName const
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Attachment: screenshot-1.png
> LocalizedMessageFactory creates new message with baseNa
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Attachment: (was: screenshot-1.png)
> LocalizedMessageFactory creates new message
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Description:
When I instantiate LocalizedMessageFactory with the String baseName const
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Description:
When I instantiate LocalizedMessageFactory with the String baseName const
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Description:
When I instantiate LocalizedMessageFactory with the String baseName const
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Description:
When I instantiate LocalizedMessageFactory with the String baseName const
[
https://issues.apache.org/jira/browse/LOG4J2-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Villablanca updated LOG4J2-2850:
--
Component/s: (was: Core)
> LocalizedMessageFactory creates new message with baseNa
Diego Villablanca created LOG4J2-2850:
-
Summary: LocalizedMessageFactory creates new message with baseName
as messagePattern
Key: LOG4J2-2850
URL: https://issues.apache.org/jira/browse/LOG4J2-2850
jvz commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631696152
@rocketraman check your account settings on https://gitbox.apache.org/setup/
and report back in that INFRA ticket I linked.
--
Peter Podniesinski created LOG4J2-2849:
--
Summary: Event Lookup Field not applying to JSON Layout additional
Property
Key: LOG4J2-2849
URL: https://issues.apache.org/jira/browse/LOG4J2-2849
Projec
jvz commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631683840
I filed https://issues.apache.org/jira/browse/INFRA-20289 to get that looked
at.
This is an automated mes
rocketraman commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631680543
> You're a committer on the project, so you should be able to merge. Make
sure you have two-factor auth set up for you github account.
I do.
--
jvz commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631679428
You're a committer on the project, so you should be able to merge. Make sure
you have two-factor auth set up for you github account.
-
rocketraman edited a comment on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631677410
> Alright, I'll merge this for you. Let me look into the permissions thing.
Ok you merged the branch as-is, with the back-and-forth on the code changes
rocketraman commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631677410
> Alright, I'll merge this for you. Let me look into the permissions thing.
Ok you merged the branch as-is, with the back-and-forth, whereas I was gonna
merg
jvz commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631676713
Alright, I'll merge this for you. Let me look into the permissions thing.
This is an automated message fro
jvz merged pull request #10:
URL: https://github.com/apache/logging-log4j-kotlin/pull/10
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
rocketraman commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631673194
Actually @jvz I don't think I have push rights to this repository. I did
modify @qoomon 's branch a little bit so if you do decide to push this
yourself, let me kn
jvz commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631656325
@rocketraman can merge this as he's been the main developer in this
component. As for a release, we'd likely need a volunteer to help do that. I
have a release guide writt
qoomon edited a comment on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631645657
when do you plan to merge and release?
This is an automated message from the Apache Git Service.
qoomon commented on pull request #10:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/10#issuecomment-631645657
when you plan to merge and release?
This is an automated message from the Apache Git Service.
To respon
Gary D. Gregory created LOG4J2-2848:
---
Summary: Create module log4j-mongodb4 to use new major version 4
Mongo driver
Key: LOG4J2-2848
URL: https://issues.apache.org/jira/browse/LOG4J2-2848
Project: L
[
https://issues.apache.org/jira/browse/LOG4J2-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on LOG4J2-2848 started by Gary D. Gregory.
---
> Create module log4j-mongodb4 to use new major version 4 Mongo driver
>
[
https://issues.apache.org/jira/browse/LOG4J2-2847?focusedWorklogId=435383&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-435383
]
ASF GitHub Bot logged work on LOG4J2-2847:
--
Author: ASF GitHub Bot
sebthom opened a new pull request #360:
URL: https://github.com/apache/logging-log4j2/pull/360
This commit modifies the Log4j-config.xsd in the following ways:
a) the type elements are re-order in a way that related types are physically
close to each other
b) the Configuration type is
Sebastian T created LOG4J2-2847:
---
Summary: Extend Log4j-config.xsd
Key: LOG4J2-2847
URL: https://issues.apache.org/jira/browse/LOG4J2-2847
Project: Log4j 2
Issue Type: Improvement
R
49 matches
Mail list logo
