[jira] [Work logged] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

2019-03-15 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2561?focusedWorklogId=214025&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-214025 ] ASF GitHub Bot logged work on LOG4J2-2561: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers commented on issue #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up

2019-03-15 Thread GitBox
rgoers commented on issue #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up URL: https://github.com/apache/logging-log4j2/pull/260#issuecomment-473435199 I'd appreciate a new PR. I have tried various options like cherry picking but never had much luck. I usually end up doin

[jira] [Work logged] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

2019-03-15 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2561?focusedWorklogId=213922&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-213922 ] ASF GitHub Bot logged work on LOG4J2-2561: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] jvz edited a comment on issue #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up

2019-03-15 Thread GitBox
jvz edited a comment on issue #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up URL: https://github.com/apache/logging-log4j2/pull/260#issuecomment-473386436 That's one simple way to do it. I don't recall if I've merged any backported commits myself, though many of the othe

[jira] [Work logged] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

2019-03-15 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2561?focusedWorklogId=213919&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-213919 ] ASF GitHub Bot logged work on LOG4J2-2561: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] jvz commented on issue #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up

2019-03-15 Thread GitBox
jvz commented on issue #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up URL: https://github.com/apache/logging-log4j2/pull/260#issuecomment-473386436 That's one simple way to do it. I don't recall if I've merged any backported commits myself, though many of the other devel

[jira] [Commented] (LOG4J2-2439) xEx{n} broken- Stacktraces are not limited by size - on ExtendedThrowablePatternConverter

2019-03-15 Thread Georgios Mournos (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793624#comment-16793624 ] Georgios Mournos commented on LOG4J2-2439: -- I fails. I attach a test case. You

[jira] [Updated] (LOG4J2-2439) xEx{n} broken- Stacktraces are not limited by size - on ExtendedThrowablePatternConverter

2019-03-15 Thread Georgios Mournos (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georgios Mournos updated LOG4J2-2439: - Attachment: TestStack.zip > xEx{n} broken- Stacktraces are not limited by size - on > E