Re: org.apache.logging.log4j.ThreadContext.pop()

Sounds appropriate for a default method, though! One day. On 8 March 2017 at 01:46, Gary Gregory wrote: > On Sun, Mar 5, 2017 at 6:43 PM, Matt Sicker wrote: > >> Looking at the code for trim(int), it seems to do the opposite actually: >> >> https://github.com/apache/logging-log4j2/blob/master/l

Re: org.apache.logging.log4j.ThreadContext.pop()

On Sun, Mar 5, 2017 at 6:43 PM, Matt Sicker wrote: > Looking at the code for trim(int), it seems to do the opposite actually: > > https://github.com/apache/logging-log4j2/blob/master/ > log4j-api/src/main/java/org/apache/logging/log4j/spi/ > MutableThreadContextStack.java#L102 > > You'd have to k

[jira] [Commented] (LOG4J2-1753) java.lang.ClassNotFoundException: org.apache.logging.log4j.core.util.ExecutorServices when running the OSGi tests

[ https://issues.apache.org/jira/browse/LOG4J2-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900861#comment-15900861 ] Gary Gregory commented on LOG4J2-1753: -- [~jvz] The tests pass now so that solves the

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

I don't see much on the user mailing lists either. Sometimes I'll post questions there myself, but I see other developers sticking to the dev lists for their own user questions. It's interesting. On 8 March 2017 at 01:16, Dominik Psenner wrote: > +1 > > I think that the activity on the user mail

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

+1 I think that the activity on the user mailing lists is low enough such that the users are not dragged away, while at the same time they take advantages of the larger audience. Further it tightens the relationship between the logging subprojects. On 2017-03-08 06:12, Stefan Bodewig wrote:

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

On Mar 8, 2017 5:28 AM, "Matt Sicker" wrote: I may be missing some mailing lists considering I just subscribed to half of them less than five minutes ago. This is a vote to merge the various Apache Logging Services mailing lists. The proposal is to combine them as follows: log4j-dev@, log4php-d

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

On 2017-03-08, Matt Sicker wrote: > I may be missing some mailing lists considering I just subscribed to half > of them less than five minutes ago. > This is a vote to merge the various Apache Logging Services mailing lists. > The proposal is to combine them as follows: > log4j-dev@, log4php-dev

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

No wait, the lazy voting thing at Commons is just the same form we use for code, just with an email plus a 72 hour notice. Makes sense for repository changes since those are a pain to reverse once the format is changed to git. On 7 March 2017 at 23:07, Matt Sicker wrote: > The -1 thing is mentio

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

The -1 thing is mentioned here regarding a -1 being a veto for anything consensus-related (generally anything to do with adding or removing committers/PMCs). I suppose in that context, a mailing list change probably falls under lazy majority, though what

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

+1 Note that generally a -1 is a veto only on code commits. On everything else it just means you are against the proposal. However, we generally strive for consensus so great weight is given to binding votes that are opposed. Ralph > On Mar 7, 2017, at 9:23 PM, Matt Sicker wrote: > > This is

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

This is my +1. If this is the incorrect voting format and we need to do a 2/3 majority instead, please veto this and let me know. This situation is not spelled out in the bylaws. On 7 March 2017 at 22:20, Matt Sicker wrote: > I may be missing some mailing lists considering I just subscribed to

[jira] [Commented] (LOG4J2-1753) java.lang.ClassNotFoundException: org.apache.logging.log4j.core.util.ExecutorServices when running the OSGi tests

[ https://issues.apache.org/jira/browse/LOG4J2-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900686#comment-15900686 ] Matt Sicker commented on LOG4J2-1753: - [~lhochet], [~garydgregory]: do you feel that

[jira] [Resolved] (LOG4J2-1835) Incorrect license info for jeromq at runtime dependencies page

[ https://issues.apache.org/jira/browse/LOG4J2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1835. - Resolution: Fixed Fix Version/s: 2.8.2 Fixed in master. Please verify and close. > Incorr

[jira] [Commented] (LOG4J2-1835) Incorrect license info for jeromq at runtime dependencies page

[ https://issues.apache.org/jira/browse/LOG4J2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900681#comment-15900681 ] ASF subversion and git services commented on LOG4J2-1835: - Commit

[VOTE] Combine the project user and dev mailing lists into user@ and dev@

I may be missing some mailing lists considering I just subscribed to half of them less than five minutes ago. This is a vote to merge the various Apache Logging Services mailing lists. The proposal is to combine them as follows: log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> d...@logging

[jira] [Assigned] (LOG4J2-1835) Incorrect license info for jeromq at runtime dependencies page

[ https://issues.apache.org/jira/browse/LOG4J2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-1835: --- Assignee: Matt Sicker > Incorrect license info for jeromq at runtime dependencies page > ---

[jira] [Resolved] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1838. - Resolution: Fixed PR merged and some documentation added to the layouts page. I noticed there are

[jira] [Commented] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900659#comment-15900659 ] ASF GitHub Bot commented on LOG4J2-1838: Github user jvz commented on the issue:

[jira] [Commented] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900655#comment-15900655 ] ASF subversion and git services commented on LOG4J2-1838: - Commit

[jira] [Commented] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900656#comment-15900656 ] ASF subversion and git services commented on LOG4J2-1838: - Commit

[jira] [Commented] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900657#comment-15900657 ] ASF GitHub Bot commented on LOG4J2-1838: Github user asfgit closed the pull reque

[jira] [Assigned] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-1838: --- Assignee: Matt Sicker > Add support for appending common suffix to each line of throwable st

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #31

See Changes: [ggregory] Refactor existing test before playing with [LOG4J2-1839] -- [..

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #31

See Changes: [ggregory] Refactor existing test before playing with [LOG4J2-1839] -- [..

[jira] [Commented] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900518#comment-15900518 ] ASF GitHub Bot commented on LOG4J2-1838: Github user xnslong commented on the iss

Re: Roadmap for 2.8.1

Yes. Scala should be released asap and the site manually modified to point to it. We would then modify the log4j source to permanently point there. Ralph > On Mar 7, 2017, at 10:09 AM, Matt Sicker wrote: > > Ralph pointed out that we can't make a release of the main repo without the > scala m

Re: Roadmap for 2.8.1

Ralph pointed out that we can't make a release of the main repo without the scala modules until there is a release of the scala modules on their own. Otherwise, there'd be a regression in the main repo by removing modules that were there before. On 7 March 2017 at 10:54, Remko Popma wrote: > No

Re: Roadmap for 2.8.1

No objection from me to release log4j-scala. Do you have a versioning scheme that lets log4j-scala and log4j upgrade independently? Sent from my iPhone > On Mar 8, 2017, at 1:42, Mikael Ståldal wrote: > > Can we release log4j-scala now? Or to we have to wait for the next release of > main r

Re: Roadmap for 2.8.1

Can we release log4j-scala now? Or to we have to wait for the next release of main repo with Scala modules removed? Should we remove the Scala modules from main repo now? On Fri, Mar 3, 2017 at 5:16 PM, Matt Sicker wrote: > The Scala language versions is already done the same standard way everyo

[jira] [Commented] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899729#comment-15899729 ] ASF GitHub Bot commented on LOG4J2-1838: Github user jvz commented on the issue:

[jira] [Commented] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace

[ https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899700#comment-15899700 ] ASF GitHub Bot commented on LOG4J2-1838: Github user xnslong commented on the iss

[jira] [Commented] (LOG4J2-1098) log4j.shutdownHookEnabled=false from log4j-web ignored?

[ https://issues.apache.org/jira/browse/LOG4J2-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899623#comment-15899623 ] Kim commented on LOG4J2-1098: - I faced a similar problem (no logging during shutdown) with lo