Jenkins build is still unstable: Log4j 2.x #2624

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Jenkins build is unstable: Log4j 2.x #2623

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: [VOTE] Release Log4j 2.8-rc1

It appears that when the main page was converted to Markdown one of the version numbers was left hard-coded. That isn’t a big deal. I will fix that before the site is deployed live. I have already updated the template. Ralph > On Jan 21, 2017, at 11:08 PM, Ralph Goers wrote: > > This is a vot

[VOTE] Release Log4j 2.8-rc1

This is a vote to release Log4j 2.8 the next version of the Log4j 2 project. Please download, test, and cast your votes on the log4j developers list. [] +1, release the artifacts [] -1, don't release because... The vote will remain open for 72 hours (or more if required). All votes are welcome a

Build failed in Jenkins: Log4j 2.x #2622

See Changes: [ralph.goers] Prepare for release -- [...truncated 4408 lines...] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.ru

Jenkins build is still unstable: Log4j 2.x #2621

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Jenkins build became unstable: Log4j 2.x #2620

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Fwd: [2/2] logging-log4j2 git commit: Use https URLs in pom

I am going to revert the change to the url in the license header as it breaks RAT. Ralph > Begin forwarded message: > > From: mattsic...@apache.org > Subject: [2/2] logging-log4j2 git commit: Use https URLs in pom > Date: January 21, 2017 at 1:40:16 PM MST > To: comm...@logging.apache.org > Rep

Build failed in Jenkins: Log4jBoot #7

See -- Started by upstream project "Log4j 2.x" build number 2619 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on beam1 (beam) in workspace

Jenkins build is back to stable : Log4j 2.x #2619

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Jenkins build is still unstable: Log4j 2.x #2618

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-1788) Create Apache Logging parent pom

[ https://issues.apache.org/jira/browse/LOG4J2-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833148#comment-15833148 ] Matt Sicker commented on LOG4J2-1788: - I've also created {{logging-parent}} branches

[jira] [Resolved] (LOG4J2-1788) Create Apache Logging parent pom

[ https://issues.apache.org/jira/browse/LOG4J2-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1788. - Resolution: Fixed Resolving this as I now have a lazy vote to release version 1. Will close when

Re: [VOTE][LAZY] Release Apache Logging Parent Pom version 1

Also, here's my +1 On 21 January 2017 at 14:55, Matt Sicker wrote: > Hello all! This is a lazy vote (as in lazy approval) to release version 1 > of the Apache Logging parent pom. > > Staging directory: https://repository.apache.org/content/ > repositories/orgapachelogging-1023/ > > Git tag: logg

[VOTE][LAZY] Release Apache Logging Parent Pom version 1

Hello all! This is a lazy vote (as in lazy approval) to release version 1 of the Apache Logging parent pom. Staging directory: https://repository.apache.org/content/repositories/orgapachelogging-1023/ Git tag: logging-parent-1 https://git-wip-us.apache.org/repos/asf?p=logging-parent.git;a=commit

[jira] [Commented] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833134#comment-15833134 ] Ralph Goers commented on LOG4J2-1768: - Can you provide a test that fails for this? I

[jira] [Commented] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833062#comment-15833062 ] A commented on LOG4J2-1768: --- And is there any workaround ? > MDC.clear() is broken in Log4j-1_

[jira] [Commented] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833061#comment-15833061 ] A commented on LOG4J2-1768: --- Sure. But is this a known issue in 2.4 ? > MDC.clear() is broken