[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057086#comment-14057086
]
Gary Gregory edited comment on LOG4J2-703 at 7/10/14 3:22 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-703.
-
Resolution: Fixed
Fix Version/s: 2.0
Committed revision 1609378.
The code now guards agai
[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-703:
Summary: Android: Could not find class 'javax.naming.InitialContext',
referenced from method org.ap
Not necessarily Groovy specifically, but in general, yes. However, even then
it might be nicer to have a layer above that that creates the Nodes and adds
them to the hierarchy. I’m not really sure what that would look like. I’d have
to try to build something before I would know what would be “
A Groovy DSL using closures would make a neat interface to creating the
Node hierarchy you're speaking of. Is that what you meant when you
mentioned this in the past?
On 9 July 2014 01:03, Ralph Goers wrote:
> IMO the proper, and recommended, way to do programmatic configuration is
> to impleme
[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056532#comment-14056532
]
Matt Sicker commented on LOG4J2-703:
Due to the runtime error of constructing JndiLook
[
https://issues.apache.org/jira/browse/LOG4J2-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056530#comment-14056530
]
Gary Gregory commented on LOG4J2-706:
-
I created and fixed [LOG4J2-707] which should h
[
https://issues.apache.org/jira/browse/LOG4J2-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-707.
-
Resolution: Fixed
Committed revision 1609251.
> Some exceptions are not logged when configuratio
Gary Gregory created LOG4J2-707:
---
Summary: Some exceptions are not logged when configuration
problems are detected
Key: LOG4J2-707
URL: https://issues.apache.org/jira/browse/LOG4J2-707
Project: Log4j 2
David Roberts created LOG4J2-706:
Summary: InvocationTargetException with RollingFileAppender in
Log4J2
Key: LOG4J2-706
URL: https://issues.apache.org/jira/browse/LOG4J2-706
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056332#comment-14056332
]
Gary Gregory edited comment on LOG4J2-703 at 7/9/14 3:24 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056333#comment-14056333
]
Matt Sicker commented on LOG4J2-703:
It's a VerifyError which means it happened at cla
[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056332#comment-14056332
]
Gary Gregory commented on LOG4J2-703:
-
Why not simply:
{noformat}
### Eclipse Workspa
[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056316#comment-14056316
]
Matt Sicker commented on LOG4J2-703:
It's worth a shot. That's the same resource I fou
[
https://issues.apache.org/jira/browse/LOG4J2-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma reassigned LOG4J2-705:
--
Assignee: Remko Popma
> Async logger loses thread context stack for events
> --
[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056024#comment-14056024
]
Nelson MELINA edited comment on LOG4J2-703 at 7/9/14 9:20 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056024#comment-14056024
]
Nelson MELINA commented on LOG4J2-703:
--
Yes [~jvz] it looks like that.
Should i just
Martin Frydl created LOG4J2-705:
---
Summary: Async logger loses thread context stack for events
Key: LOG4J2-705
URL: https://issues.apache.org/jira/browse/LOG4J2-705
Project: Log4j 2
Issue Type:
18 matches
Mail list logo
