[jira] [Commented] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15752237#comment-15752237 ] Gary Gregory commented on LOG4J2-1740: -- Can you please provide your configuration file? How about a

[jira] [Resolved] (LOG4J2-1340) AsyncLogger's Ringbuffer holding all JVM memory

2016-12-15 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1340. - Resolution: Not A Problem Assignee: Remko Popma Resolving this issue as "not a problem".

[jira] [Commented] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15752989#comment-15752989 ] Gary Gregory commented on LOG4J2-1740: -- I do not think you _always_ want to have the start of a

Build failed in Jenkins: Log4j 2.x #2540

2016-12-15 Thread Apache Jenkins Server
See Changes: [ggregory] Fix swapped debugging message arguments. -- [...truncated 3634 lines...] at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at

[jira] [Commented] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753017#comment-15753017 ] Ralph Goers commented on LOG4J2-1740: - I agree. I would hope that we could create it dynamically if

[jira] [Resolved] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1740. -- Resolution: Fixed Fix Version/s: 2.8 Ralph, Would you mind giving a look over my fix

[jira] [Created] (LOG4J2-1741) scala: add support for creating custom plugins

2016-12-15 Thread PJ Fanning (JIRA)
PJ Fanning created LOG4J2-1741: -- Summary: scala: add support for creating custom plugins Key: LOG4J2-1741 URL: https://issues.apache.org/jira/browse/LOG4J2-1741 Project: Log4j 2 Issue Type:

[jira] [Created] (LOG4J2-1742) scala: add support for creating custom plugins

2016-12-15 Thread PJ Fanning (JIRA)
PJ Fanning created LOG4J2-1742: -- Summary: scala: add support for creating custom plugins Key: LOG4J2-1742 URL: https://issues.apache.org/jira/browse/LOG4J2-1742 Project: Log4j 2 Issue Type:

[jira] [Commented] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15752791#comment-15752791 ] Gary Gregory commented on LOG4J2-1740: -- You should see if you can create a failing test in

[jira] [Closed] (LOG4J2-1742) scala: add support for creating custom plugins

2016-12-15 Thread PJ Fanning (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PJ Fanning closed LOG4J2-1742. -- Resolution: Duplicate > scala: add support for creating custom plugins >

Jenkins build is back to normal : Log4j 2.x #2541

2016-12-15 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Peter Nimmervoll (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753727#comment-15753727 ] Peter Nimmervoll commented on LOG4J2-1740: -- Tried the latest Git master and it is fixed now. >

[jira] [Commented] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15751072#comment-15751072 ] Gary Gregory commented on LOG4J2-1740: -- I fixed that in commit

[jira] [Updated] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Peter Nimmervoll (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Nimmervoll updated LOG4J2-1740: - Description: When i try to add a RollingFileAppender with a CronTriggeringPolicy

[jira] [Created] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Peter Nimmervoll (JIRA)
Peter Nimmervoll created LOG4J2-1740: Summary: Add CronTriggeringPolicy programmatically leads to NPE Key: LOG4J2-1740 URL: https://issues.apache.org/jira/browse/LOG4J2-1740 Project: Log4j 2

[jira] [Commented] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750920#comment-15750920 ] Gary Gregory commented on LOG4J2-1740: -- Can you please add a stack trace to your description? > Add

[jira] [Commented] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Peter Nimmervoll (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15751155#comment-15751155 ] Peter Nimmervoll commented on LOG4J2-1740: -- Based on the commit I'm not convinced this will work

[jira] [Commented] (LOG4J2-1740) Add CronTriggeringPolicy programmatically leads to NPE

2016-12-15 Thread Peter Nimmervoll (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15751284#comment-15751284 ] Peter Nimmervoll commented on LOG4J2-1740: -- Ok, I tried the current Git master and the problem