[jira] [Updated] (LOG4J2-1841) Problems with consequences after LOG4J2-248

[ https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated LOG4J2-1841: --- Description: Situation till Log4j v. 2.5 (including it): 1. One

[jira] [Updated] (LOG4J2-1841) Problems with consequences after LOG4J2-248

[ https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated LOG4J2-1841: --- Description: Situation till Log4j v. 2.5 (including it): 1. One

[jira] [Created] (LOG4J2-1841) Problems with consequences after LOG4J2-248

Seweryn Habdank-Wojewodzki created LOG4J2-1841: -- Summary: Problems with consequences after LOG4J2-248 Key: LOG4J2-1841 URL: https://issues.apache.org/jira/browse/LOG4J2-1841 Project:

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

See Changes: [xnslong] add suffix options, this options is supposed to be a pattern layout [xnslong] Allow to append a suffix

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

See Changes: [xnslong] add suffix options, this options is supposed to be a pattern layout [xnslong] Allow to append a suffix

Roadmap for log4j-api-scala 11.0

We've established that this will need to be released before we can officially remove the equivalent modules from the main log4j repository (and release cycle). Since the artifacts are no longer tied directly to log4j-api/core, we've also agreed that it makes sense to version it separately as well.

Re: Roadmap for 2.8.1

I've done a couple releases in this project so far (a Log4j and Logging Parent release), so it shouldn't be too hard. I'm thinking we need to copy over the log4j-distribution stuff so we can create source and binary assemblies for uploading to apache.org as well. On 8 March 2017 at 11:55, Mikael

[jira] [Commented] (LOG4J2-444) Log4j2 eclipselink integration

[ https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902024#comment-15902024 ] Mike Calmus commented on LOG4J2-444: While that Wiki entry is helpful, it isn't exactly a solution.

[jira] [Created] (LOG4J2-1840) Doc issue in example for regex

pradeep bala created LOG4J2-1840: Summary: Doc issue in example for regex Key: LOG4J2-1840 URL: https://issues.apache.org/jira/browse/LOG4J2-1840 Project: Log4j 2 Issue Type: Documentation

Re: Roadmap for 2.8.1

I have never made any Apache release before, so it's probably good if someone more experienced does it the first time. So I would be grateful if Matt could do it. I can maybe do it the next time. On Mar 8, 2017 5:43 PM, "Matt Sicker" wrote: > If you don't have time to do it,

[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=15901646#comment-15901646 ] ASF GitHub Bot commented on LOG4J2-1838: Github user xnslong 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=15901613#comment-15901613 ] 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=15901595#comment-15901595 ] ASF GitHub Bot commented on LOG4J2-1838: Github user xnslong commented on the issue:

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

Guten Tag Apache, am Mittwoch, 8. März 2017 um 13:38 schrieben Sie: > The reason for doing this is a result of the last board meeting. > The PMC had to discuss something on the private mailing list simply > because PMC members don't subscribe to every list, nor do they want > to, so it was not

[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=15901529#comment-15901529 ] ASF GitHub Bot commented on LOG4J2-1838: Github user rgoers commented on the issue:

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

Based on the voting so far, it looks like merging user lists isn't desired. I'm cool with that, so I'll -1 the user list merge as well. I'm still +1 for merging developer lists unless someone has a better idea. We shouldn't have to rely on the private list for public discussions. On 8 March 2017

[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=15901517#comment-15901517 ] ASF GitHub Bot commented on LOG4J2-1838: Github user jvz commented on the issue:

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

The reason for doing this is a result of the last board meeting. The PMC had to discuss something on the private mailing list simply because PMC members don't subscribe to every list, nor do they want to, so it was not possible to have the discussion on the correct mailing list. Ralph > On

[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=15901179#comment-15901179 ] ASF GitHub Bot commented on LOG4J2-1838: Github user remkop commented on the issue:

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

log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> d...@logging.apache.org +1 log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, general@ -> u...@logging.apache.org Interesting discussion. I can see both pros and cons. How will this work for users currently subscribed to

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

> log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> d...@logging.apache.org +0 I can see some benefits, but I think that most developers outside of the PMC are like regular users and only care about one about the projects. > log4j-user@, log4php-user@, log4net-user@, log4cxx-user@,