[jira] [Commented] (LOG4J2-741) Reinstate the package attribute for discovering custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075559#comment-14075559 ] Remko Popma commented on LOG4J2-741: About the registry.clear in {{addPackage}}, I see

[jira] [Resolved] (LOG4J2-749) Retain the default date pattern after fixing ISO8601_PATTERN

[ https://issues.apache.org/jira/browse/LOG4J2-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-749. Resolution: Fixed > Retain the default date pattern after fixing ISO8601_PATTERN >

[jira] [Commented] (LOG4J2-749) Retain the default date pattern after fixing ISO8601_PATTERN

[ https://issues.apache.org/jira/browse/LOG4J2-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1407#comment-1407 ] Remko Popma commented on LOG4J2-749: Applied Scott's patch (attached to LOG4J2-670) wi

Re: build fail (file locking with JDK 8.0.5?)

Hm, instead of java 8, the problem may have been related to the date pattern? I don't see how, but after applying Scott's patch the problem went away, and I can build and test with java 8 again... Very strange... On Sun, Jul 27, 2014 at 1:57 PM, Remko Popma wrote: > I tried three times in a row

build fail (file locking with JDK 8.0.5?)

I tried three times in a row, but the build gets stuck here: Failed tests: FileAppenderTest.testMultipleLockedAppenders Could not delete target\fileAppenderTest.log, last modifed 14/07/27 13:13 FileAppenderTest.testLockingAppender Could not delete target\fileAppenderTest.log, last modifed 14/0

[jira] [Assigned] (LOG4J2-749) Retain the default date pattern after fixing ISO8601_PATTERN

[ https://issues.apache.org/jira/browse/LOG4J2-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-749: -- Assignee: Remko Popma > Retain the default date pattern after fixing ISO8601_PATTERN >

[jira] [Updated] (LOG4J2-749) Retain the default date pattern after fixing ISO8601_PATTERN

[ https://issues.apache.org/jira/browse/LOG4J2-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-749: --- Description: Scott Harrington correctly pointed out the following (from comments on LOG4J2-670): Yo

[jira] [Commented] (LOG4J2-670) DatePatternConverter ISO8601_PATTERN does not conform to ISO8601

[ https://issues.apache.org/jira/browse/LOG4J2-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075533#comment-14075533 ] Remko Popma commented on LOG4J2-670: I agree. I created a new issue, LOG4J2-749, for t

[jira] [Created] (LOG4J2-749) Retain the default date pattern after fixing ISO8601_PATTERN

Remko Popma created LOG4J2-749: -- Summary: Retain the default date pattern after fixing ISO8601_PATTERN Key: LOG4J2-749 URL: https://issues.apache.org/jira/browse/LOG4J2-749 Project: Log4j 2 Iss

[jira] [Updated] (LOG4J2-670) DatePatternConverter ISO8601_PATTERN does not conform to ISO8601

[ https://issues.apache.org/jira/browse/LOG4J2-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Harrington updated LOG4J2-670: Attachment: log4j-r1613644-LOG4J2-670-patch.txt If you agree with my 'DEFAULT' suggestion,

[jira] [Commented] (LOG4J2-670) DatePatternConverter ISO8601_PATTERN does not conform to ISO8601

[ https://issues.apache.org/jira/browse/LOG4J2-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075514#comment-14075514 ] Scott Harrington commented on LOG4J2-670: - You're going to get complaints from mor

[jira] [Comment Edited] (LOG4J2-747) Servlet Example of using different log4j2-{env:envValue}.xml

[ https://issues.apache.org/jira/browse/LOG4J2-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075510#comment-14075510 ] A B edited comment on LOG4J2-747 at 7/26/14 11:28 PM: -- FYI. I also t

[jira] [Commented] (LOG4J2-747) Servlet Example of using different log4j2-{env:envValue}.xml

[ https://issues.apache.org/jira/browse/LOG4J2-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075510#comment-14075510 ] A B commented on LOG4J2-747: FYI. I also tried with absolute path, the results were the same

[jira] [Updated] (LOG4J2-748) Erroneous references to log4j classes appearing in online documentation

[ https://issues.apache.org/jira/browse/LOG4J2-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Bisson updated LOG4J2-748: Priority: Minor (was: Major) > Erroneous references to log4j classes appearing in online documenta

[jira] [Resolved] (LOG4J2-748) Erroneous references to log4j classes appearing in online documentation

[ https://issues.apache.org/jira/browse/LOG4J2-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Bisson resolved LOG4J2-748. - Resolution: Fixed Fix Version/s: 2.0.1 > Erroneous references to log4j classes appearing i

[jira] [Created] (LOG4J2-748) Erroneous references to log4j classes appearing in online documentation

Roger Bisson created LOG4J2-748: --- Summary: Erroneous references to log4j classes appearing in online documentation Key: LOG4J2-748 URL: https://issues.apache.org/jira/browse/LOG4J2-748 Project: Log4j 2

[jira] [Comment Edited] (LOG4J2-741) Reinstate the package attribute for discovering custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075456#comment-14075456 ] Matt Sicker edited comment on LOG4J2-741 at 7/26/14 6:26 PM: -

[jira] [Commented] (LOG4J2-741) Reinstate the package attribute for discovering custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075456#comment-14075456 ] Matt Sicker commented on LOG4J2-741: All looks good! > Reinstate the package attribut

[jira] [Updated] (LOG4J2-698) How does log4j2 handle daylight savings?

[ https://issues.apache.org/jira/browse/LOG4J2-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-698: --- Description: How come does not produce the same log timestamp as ? Isn't CST GMT-5 right now? It'

[jira] [Comment Edited] (LOG4J2-698) How does log4j2 handle daylight savings?

[ https://issues.apache.org/jira/browse/LOG4J2-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075414#comment-14075414 ] Remko Popma edited comment on LOG4J2-698 at 7/26/14 3:13 PM: -

[jira] [Commented] (LOG4J2-698) How does log4j2 handle daylight savings?

[ https://issues.apache.org/jira/browse/LOG4J2-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075414#comment-14075414 ] Remko Popma commented on LOG4J2-698: Bryan, does Scott's comment solve the problem? >

[jira] [Updated] (LOG4J2-461) (Android) ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger

[ https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-461: --- Summary: (Android) ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger

[jira] [Updated] (LOG4J2-461) (Android) ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger

[ https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-461: --- Labels: Android (was: ) > (Android) ERROR StatusLogger Unable to locate a logging implementation,

[jira] [Updated] (LOG4J2-565) Log4j2 loading time on single-board (embedded) computers

[ https://issues.apache.org/jira/browse/LOG4J2-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-565: --- Summary: Log4j2 loading time on single-board (embedded) computers (was: Log4j2 loading time) > Log4

[jira] [Resolved] (LOG4J2-670) DatePatternConverter ISO8601_PATTERN does not conform to ISO8601

[ https://issues.apache.org/jira/browse/LOG4J2-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-670. Resolution: Fixed Fix Version/s: 2.0.1 Fixed in revision 1613644. Please verify and close.

[jira] [Assigned] (LOG4J2-670) DatePatternConverter ISO8601_PATTERN does not conform to ISO8601

[ https://issues.apache.org/jira/browse/LOG4J2-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-670: -- Assignee: Remko Popma > DatePatternConverter ISO8601_PATTERN does not conform to ISO8601 >

[jira] [Closed] (LOG4J2-537) application does not end.

[ https://issues.apache.org/jira/browse/LOG4J2-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-537. -- Resolution: Not a Problem Closing this issue as "not a problem" for lack of response from the reporter

[jira] [Closed] (LOG4J2-432) Fallback when old configuration method is used in servlet 3.0+ container.

[ https://issues.apache.org/jira/browse/LOG4J2-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-432. -- Resolution: Fixed Fix Version/s: 2.0-rc1 Closing this issue as the reporter confirmed the proble

[jira] [Updated] (LOG4J2-747) Servlet Example of using different log4j2-{env:envValue}.xml

[ https://issues.apache.org/jira/browse/LOG4J2-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-747: --- Description: Based on my previous post / question on the log4j2 user list - Defining different log4j

[jira] [Updated] (LOG4J2-747) Servlet Example of using different log4j2-{env:envValue}.xml

[ https://issues.apache.org/jira/browse/LOG4J2-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated LOG4J2-747: --- Attachment: LOG4J2747_Jira_Sample3.ear The earlier war that I attached was part of the project where I also have an

Re: 2.0.1 and Android

Done with LOG4J2-741, reviews would be welcome. If 2.0.1 can't go out this weekend then so be it. It can wait another week or so. Good luck both with moving house and good luck Ralph with the upcoming surgery. On Sat, Jul 26, 2014 at 1:26 PM, Ralph Goers wrote: > I am happy to do the release b

[jira] [Updated] (LOG4J2-714) To Switch to Synchronous mode when there is an issue with PERSISTENT Database used in Flume Appender

[ https://issues.apache.org/jira/browse/LOG4J2-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-714: --- Priority: Major (was: Blocker) Re-resetting priority to major as this is not a showstopper for 2.0.1

[jira] [Resolved] (LOG4J2-746) Custom Appender

[ https://issues.apache.org/jira/browse/LOG4J2-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-746. Resolution: Duplicate Fix Version/s: 2.0.1 Resolving this as a duplicate of LOG4J2-741. LOG4

[jira] [Resolved] (LOG4J2-743) How to add a custom appender

[ https://issues.apache.org/jira/browse/LOG4J2-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-743. Resolution: Duplicate Fix Version/s: 2.0.1 Resolving this as a duplicate of LOG4J2-741. LOG

[jira] [Resolved] (LOG4J2-741) Reinstate the package attribute for discovering custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-741. Resolution: Fixed Fixed in revision 1613615. Added a JUnit test with a custom plugin loaded via a