[jira] [Assigned] (LOG4J2-154) ThreadContext performance improvement: shallow copies for reads, deep copies for writes

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-154: -- Assignee: Remko Popma > ThreadContext performance improvement: shallow copies for reads, de

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660209#comment-13660209 ] Remko Popma commented on LOG4J2-255: That is great, thanks for the confirmation! I th

[jira] [Commented] (LOG4J2-263) RFC5424 Layout (and Syslog Layout) uses platform encoding when no charset is specified in configuration

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660203#comment-13660203 ] Gary Gregory commented on LOG4J2-263: - I do not know enough about this appender and la

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660199#comment-13660199 ] Gary Gregory commented on LOG4J2-255: - I think am resigned to the fact that we have to

[jira] [Commented] (LOG4J2-263) RFC5424 Layout (and Syslog Layout) uses platform encoding when no charset is specified in configuration

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660176#comment-13660176 ] Remko Popma commented on LOG4J2-263: I had some trouble parsing the RFC text, that's w

[jira] [Comment Edited] (LOG4J2-263) RFC5424 Layout (and Syslog Layout) uses platform encoding when no charset is specified in configuration

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660165#comment-13660165 ] Gary Gregory edited comment on LOG4J2-263 at 5/16/13 11:58 PM: -

[jira] [Comment Edited] (LOG4J2-263) RFC5424 Layout (and Syslog Layout) uses platform encoding when no charset is specified in configuration

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660165#comment-13660165 ] Gary Gregory edited comment on LOG4J2-263 at 5/16/13 11:56 PM: -

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660168#comment-13660168 ] Remko Popma commented on LOG4J2-255: Looks like this was a fruitful discussion: 5 new

[jira] [Commented] (LOG4J2-263) RFC5424 Layout (and Syslog Layout) uses platform encoding when no charset is specified in configuration

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660165#comment-13660165 ] Gary Gregory commented on LOG4J2-263: - In this spec https://tools.ietf.org/html/rfc542

Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 7:30 PM, Scott Deboy wrote: > http://www.jetbrains.com/idea/buy/buy.jsp#openSource > Thank you! Gary > > On 5/16/13, Gary Gregory wrote: > > On Thu, May 16, 2013 at 6:04 PM, Nick Williams < > > nicho...@nicholaswilliams.net> wrote: > > > >> I don't use Eclipse (can't

Re: Module clean ups

2013-05-16 Thread Scott Deboy
http://www.jetbrains.com/idea/buy/buy.jsp#openSource On 5/16/13, Gary Gregory wrote: > On Thu, May 16, 2013 at 6:04 PM, Nick Williams < > nicho...@nicholaswilliams.net> wrote: > >> I don't use Eclipse (can't stand the thing), so I hesitate to hazard a >> guess. My gut feeling is it sounds like a

Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 6:04 PM, Nick Williams < nicho...@nicholaswilliams.net> wrote: > I don't use Eclipse (can't stand the thing), so I hesitate to hazard a > guess. My gut feeling is it sounds like a bug in the Maven Eclipse Plugin. > The error message and URL definitely indicates that the err

Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 6:04 PM, Nick Williams < nicho...@nicholaswilliams.net> wrote: > I don't use Eclipse (can't stand the thing), so I hesitate to hazard a > guess. > Flame bait! :) > My gut feeling is it sounds like a bug in the Maven Eclipse Plugin. The > error message and URL definitely

[jira] [Created] (LOG4J2-263) RFC5424 Layout (and Syslog Layout) uses platform encoding when no charset is specified in configuration

2013-05-16 Thread Remko Popma (JIRA)
Remko Popma created LOG4J2-263: -- Summary: RFC5424 Layout (and Syslog Layout) uses platform encoding when no charset is specified in configuration Key: LOG4J2-263 URL: https://issues.apache.org/jira/browse/LOG4J2-263

[jira] [Updated] (LOG4J2-262) FlumeAppender should allow interceptors to be specified on embedded agent

2013-05-16 Thread Edward Sargisson (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Sargisson updated LOG4J2-262: Attachment: log4j2-interceptors.diff > FlumeAppender should allow interceptors to be sp

[jira] [Created] (LOG4J2-262) FlumeAppender should allow interceptors to be specified on embedded agent

2013-05-16 Thread Edward Sargisson (JIRA)
Edward Sargisson created LOG4J2-262: --- Summary: FlumeAppender should allow interceptors to be specified on embedded agent Key: LOG4J2-262 URL: https://issues.apache.org/jira/browse/LOG4J2-262 Project

Re: Inconsistency in import ordering

2013-05-16 Thread Scott Deboy
Sure, add them to the wiki please. On 5/16/13, Nick Williams wrote: > CheckStyle ImportOrder changes committed. > > I also committed the changes necessary to rid all database appender and tag > library classes of CheckStyle ImportOrder errors. > > I will continue to work on reordering imports in

Re: Inconsistency in import ordering

2013-05-16 Thread Nick Williams
CheckStyle ImportOrder changes committed. I also committed the changes necessary to rid all database appender and tag library classes of CheckStyle ImportOrder errors. I will continue to work on reordering imports in other classes. To prevent these CheckStyle errors from coming back, we should

Re: Module clean ups

2013-05-16 Thread Nick Williams
I don't use Eclipse (can't stand the thing), so I hesitate to hazard a guess. My gut feeling is it sounds like a bug in the Maven Eclipse Plugin. The error message and URL definitely indicates that the error originated in the plugin. I would try running with -e to see the full error stack trace.

Re: Module clean ups

2013-05-16 Thread Gary Gregory
Nice work Nick. The last wrinkle for Eclipse users is that running, which is not new, is running "mvn eclipse:eclipse" works until the last sample: [INFO] Apache Log4j 2 SUCCESS [1.101s] [INFO] Apache Log4j API .. SUCCESS [0.256

Re: Jackson 1.x vs 2.x

2013-05-16 Thread Nick Williams
Ok. By the way, in the process of doing this I was able to resolve ALL dependency convergence issues in the dependency convergence reports. Nick On May 16, 2013, at 1:18 PM, Ralph Goers wrote: > Well, if they changed the package names so there is no conflict then I guess > we will have to hav

Re: Module clean ups

2013-05-16 Thread Nick Williams
- There were >400 use cases of "Log4j" in documentation, but around 100 use cases of "Log4J." All uses of "Log4J" have been changed to "Log4j." - There were dozens of classes with "Log4j" in their names, but a handful had "Log4J" in their name. All uses of "Log4J" have been changed to "Log4j."

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659933#comment-13659933 ] Gary Gregory commented on LOG4J2-255: - A couple of data points for testing and the rec

Re: Jackson 1.x vs 2.x

2013-05-16 Thread Ralph Goers
Well, if they changed the package names so there is no conflict then I guess we will have to have both versions. Ralph On May 16, 2013, at 11:07 AM, Nick Williams wrote: > It's not just the groupId/artifactId that changed between Jackson 1 and > Jackson 2. It's the Java package, too. Simply ex

Re: Module clean ups

2013-05-16 Thread Ralph Goers
Yes. That way both log4j 1.x and log4j 2.x configuration files can be present. Ralph On May 16, 2013, at 11:10 AM, Gary Gregory wrote: > On Thu, May 16, 2013 at 2:07 PM, Ralph Goers > wrote: > We decided a while ago not to include the "2" in the Log4j name. It is > enough that it is in the

Re: Module clean ups

2013-05-16 Thread Ralph Goers
Not someone :-) me. Notice that only beta5 is there. I didn't do it in beta6. I need to update the wiki to remind myself not to do it in the future (or whoever else does the release). Ralph On May 16, 2013, at 11:08 AM, Nick Williams wrote: > Then in appears someone broke that. The samples

Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 2:07 PM, Ralph Goers wrote: > We decided a while ago not to include the "2" in the Log4j name. It is > enough that it is in the version number. > But the "2" remains in the name of the default configuration files. Is that on purpose? Gary > Ralph > > On May 16, 2013, a

Re: Module clean ups

2013-05-16 Thread Nick Williams
Then in appears someone broke that. The samples are, indeed, in Maven Central: http://search.maven.org/#search%7Cga%7C1%7Corg.apache.logging.log4j.samples Nick On May 16, 2013, at 1:06 PM, Ralph Goers wrote: > The release wiki doesn't say it but the samples are excluded from releases to > Mave

Re: Module clean ups

2013-05-16 Thread Nick Williams
A valid point. I won't add 2. But what about the parent POM? It has 2 in the name. Should that be removed? On May 16, 2013, at 1:07 PM, Ralph Goers wrote: > We decided a while ago not to include the "2" in the Log4j name. It is > enough that it is in the version number. > > Ralph > > On May

Re: Jackson 1.x vs 2.x

2013-05-16 Thread Nick Williams
It's not just the groupId/artifactId that changed between Jackson 1 and Jackson 2. It's the Java package, too. Simply excluding Flume's dependency on 1.x and introducing a dependency on 2.x doesn't work. Flume classes literally don't load due to NoClassDefFound errors. N On May 16, 2013, at 1:

Re: Module clean ups

2013-05-16 Thread Ralph Goers
We decided a while ago not to include the "2" in the Log4j name. It is enough that it is in the version number. Ralph On May 16, 2013, at 10:43 AM, Nick Williams wrote: > If I understand correctly, you want the last four (all samples) to be: > > log4j-samples > log4j-samples-common > log4j-sa

Re: Module clean ups

2013-05-16 Thread Ralph Goers
The release wiki doesn't say it but the samples are excluded from releases to Maven Central. I believe the sample jars are also not included in the binary distribution. Ralph On May 16, 2013, at 10:31 AM, Gary Gregory wrote: > Right now we have, as seen in M3 output: > > [INFO] Apache Log4j

Re: Jackson 1.x vs 2.x

2013-05-16 Thread Ralph Goers
The master log4j pom.xml should have a version for jackson in the dependency management section. That version should replace any transitive dependencies. However, if the groupId has changed then that doesn't work. You would have to add the Jackson 2 dependencies to flume-ng's pom.xml and exclude

Re: Inconsistency in import ordering

2013-05-16 Thread Gary Gregory
+1 Gary On Thu, May 16, 2013 at 1:45 PM, Nick Williams < nicho...@nicholaswilliams.net> wrote: > I haven't heard any objections to this suggestion. I'm going to move > forward with it later this afternoon if nobody objects before then. > > Thanks, > > Nick > > On May 13, 2013, at 11:06 AM, Nick

Re: Module clean ups

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 1:43 PM, Nick Williams < nicho...@nicholaswilliams.net> wrote: > If I understand correctly, you want the last four (all samples) to be: > > log4j-samples > log4j-samples-common > log4j-samples-remote > log4j-samples-embedded > > And you also want them to have names as appos

Re: Inconsistency in import ordering

2013-05-16 Thread Nick Williams
I haven't heard any objections to this suggestion. I'm going to move forward with it later this afternoon if nobody objects before then. Thanks, Nick On May 13, 2013, at 11:06 AM, Nick Williams wrote: > I've noticed a lot of inconsistence in import ordering, and importantly I've > also notice

Re: Module clean ups

2013-05-16 Thread Nick Williams
If I understand correctly, you want the last four (all samples) to be: log4j-samples log4j-samples-common log4j-samples-remote log4j-samples-embedded And you also want them to have names as apposed to just IDs. I'll make some further observations: - Core and JMX GUI should start with "Apache Lo

Re: Jackson 1.x vs 2.x

2013-05-16 Thread Nick Williams
Yes, J1 and J2 are in different packages, but Core IS using v2. log4j-core has a compile-time dependency on 2.x and NO dependency on 1.x (previously its compile-time dependency was on 1.x). This temporarily (locally) broke compilation in the JSON config classes but I changed the import statemen

Re: Jackson 1.x vs 2.x

2013-05-16 Thread Gary Gregory
On Thu, May 16, 2013 at 1:28 PM, Gary Gregory wrote: > FWIW, it look like Avro 1.7.4 still depends on Jackson 1.8.8. > > I'd go with solution (3) and let other dependencies catch up to modern > versions of Jackson but... > > It looks like J1 and J2 are in different packages right? v2 in > com.fast

Module clean ups

2013-05-16 Thread Gary Gregory
Right now we have, as seen in M3 output: [INFO] Apache Log4j 2 [INFO] Apache Log4j API [INFO] Apache Log4J Core [INFO] Apache Log4j 1.x Compatibility API [INFO] Apache Log4j SLF4J Binding [INFO] Apache Log4j to SLF4J Adapter [INFO] Apache Log4j Commons Logging Bridge [INFO] Apache Log4j Flume NG B

Re: Jackson 1.x vs 2.x

2013-05-16 Thread Gary Gregory
FWIW, it look like Avro 1.7.4 still depends on Jackson 1.8.8. I'd go with solution (3) and let other dependencies catch up to modern versions of Jackson but... It looks like J1 and J2 are in different packages right? v2 in com.fasterxml.jackson and v1 in org.codehaus.jackson? So if you changed a

Re: Jackson 1.x vs 2.x

2013-05-16 Thread Nick Williams
So this is all kinds of fun... log4j-core depends on: jackson 1.9.11 (optional) log4j-flume-ng depends on: flume-ng-sdk 1.3.1 depends on: avro 1.7.2 depends on: jackson 1.8.8 flume-embedded (sample) depends on: flume-ng-sdk 1.3.1 depends on: avro 1.7.2 depen

[jira] [Created] (LOG4J2-261) Incorrect error message if agent name specified in Flume appender properties

2013-05-16 Thread Edward Sargisson (JIRA)
Edward Sargisson created LOG4J2-261: --- Summary: Incorrect error message if agent name specified in Flume appender properties Key: LOG4J2-261 URL: https://issues.apache.org/jira/browse/LOG4J2-261 Proj

[jira] [Resolved] (LOG4J2-260) XML layout does not specify charset in content type

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-260. - Resolution: Fixed {noformat} commit -m "[LOG4J2-260] XML layout does not specify charset in conte

[jira] [Resolved] (LOG4J2-259) HTML layout does not specify charset in content type

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-259. - Resolution: Fixed {noformat} commit -m "[LOG4J2-259] HTML layout does not specify charset in cont

[jira] [Created] (LOG4J2-260) XML layout does not specify charset in content type

2013-05-16 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-260: --- Summary: XML layout does not specify charset in content type Key: LOG4J2-260 URL: https://issues.apache.org/jira/browse/LOG4J2-260 Project: Log4j 2 Issue Type:

[jira] [Updated] (LOG4J2-260) XML layout does not specify charset in content type

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-260: Description: XML layout does not specify charset in content type (was: HTML layout does not specif

[jira] [Comment Edited] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659654#comment-13659654 ] Remko Popma edited comment on LOG4J2-255 at 5/16/13 3:59 PM: -

[jira] [Created] (LOG4J2-259) HTML layout does not specify charset in content type

2013-05-16 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-259: --- Summary: HTML layout does not specify charset in content type Key: LOG4J2-259 URL: https://issues.apache.org/jira/browse/LOG4J2-259 Project: Log4j 2 Issue Type

[jira] [Resolved] (LOG4J2-258) HTML layout does not output meta element for charset.

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-258. - Resolution: Fixed {noformat} commit -m "[LOG4J2-258] HTML layout does not output meta element for

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659654#comment-13659654 ] Remko Popma commented on LOG4J2-255: Gary, I actually think you are hitting the same p

[jira] [Created] (LOG4J2-258) HTML layout does not output meta element for charset.

2013-05-16 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-258: --- Summary: HTML layout does not output meta element for charset. Key: LOG4J2-258 URL: https://issues.apache.org/jira/browse/LOG4J2-258 Project: Log4j 2 Issue Typ

[jira] [Resolved] (LOG4J2-257) XML layout ignores charset for the XML processing intruction's encoding attribute

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-257. - Resolution: Fixed {noformat} commit -m "[LOG4J2-257] XML layout ignores charset for the XML proce

[jira] [Created] (LOG4J2-257) XML layout ignores charset for the XML processing intruction's encoding attribute

2013-05-16 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-257: --- Summary: XML layout ignores charset for the XML processing intruction's encoding attribute Key: LOG4J2-257 URL: https://issues.apache.org/jira/browse/LOG4J2-257 Project

[jira] [Updated] (LOG4J2-160) Include option in throwable pattern converter to control stack trace separator

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-160: Fix Version/s: (was: 2.0-beta6) 2.0-beta7 > Include option in throwable

[jira] [Updated] (LOG4J2-159) log4j.xml loading from classpath not working correct in osgi environment

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-159: Fix Version/s: (was: 2.0-beta6) 2.0-beta7 > log4j.xml loading from class

[jira] [Updated] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-223: Fix Version/s: (was: 2.0-beta6) 2.0-beta7 > IlliegalStateException throw

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659605#comment-13659605 ] Gary Gregory commented on LOG4J2-255: - {quote} Data read from files or other non-netwo

[jira] [Comment Edited] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659601#comment-13659601 ] Gary Gregory edited comment on LOG4J2-255 at 5/16/13 2:51 PM: --

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659601#comment-13659601 ] Gary Gregory commented on LOG4J2-255: - I want to see the correct chars on Windows, so

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659598#comment-13659598 ] Remko Popma commented on LOG4J2-255: You mean, in order to reproduce the issue? Perhap

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659582#comment-13659582 ] Gary Gregory commented on LOG4J2-255: - What encoding should I used in the layout for t

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Nick Williams (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659577#comment-13659577 ] Nick Williams commented on LOG4J2-255: -- I like that plan: - XMLLayout and HTMLLayout

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Nick Williams (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659578#comment-13659578 ] Nick Williams commented on LOG4J2-255: -- It's about time! _Finally_ I can {{}} when I

[jira] [Comment Edited] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659572#comment-13659572 ] Remko Popma edited comment on LOG4J2-255 at 5/16/13 2:25 PM: -

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659572#comment-13659572 ] Remko Popma commented on LOG4J2-255: Yay! Fancy wiki formatting!! Yippee!

[jira] [Comment Edited] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659559#comment-13659559 ] Remko Popma edited comment on LOG4J2-255 at 5/16/13 2:21 PM: -

[jira] [Updated] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-255: Description: When I tried to log a Japanese string the output was scrambled in both the Console an

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659559#comment-13659559 ] Remko Popma commented on LOG4J2-255: Nick, nice find on the header being hard-coded to

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Nick Williams (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659476#comment-13659476 ] Nick Williams commented on LOG4J2-255: -- Okay, I think I understand all of this better

BurstFilter

2013-05-16 Thread Christian Grobmeier
Hi, https://issues.apache.org/bugzilla/show_bug.cgi?id=45753 it has a BurstFilter for companions, but later I saw some comments by Ralph it arrived in log4j 2. So I think we should close this issue and refer people to log4j 2 in this case. Any objections? Cheers Christian -- http://www.grobmei

[Bug 41006] Contributing XMLSocketHubReceiver

2013-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=41006 --- Comment #5 from grobmeier --- Thanks for this Receiver! I know it has been a while and might not have an interest any longer. But if you have, would it be possible to send junit tests along? Thanks! -- You are receiving this mail b

[Bug 53536] RollingFileAppender with TimeBasedRolling policy doesn't create parent-path if FileNamePattern contains date pattern as directory

2013-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53536 grobmeier changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 53417] Extras TimeBasedRollingPolicy does not compress log files

2013-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53417 grobmeier changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 51152] RollingFileAppender of companion/extras 1.1 contains possible race condition

2013-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=51152 grobmeier changed: What|Removed |Added CC||krisztian.kocsis@optimaster

[Bug 49390] 1.0 releases of log4j companions component and receivers

2013-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=49390 grobmeier changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 47595] [companion] POMs of companions have problems

2013-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47595 grobmeier changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 53645] DBAppender has a compile error

2013-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53645 grobmeier changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

New log4j-extras snapshot

2013-05-16 Thread Christian Grobmeier
Hi all, just made a snapshot for the upcoming log4j extras 1.2.17 release which I plan to start soon. https://repository.apache.org/content/repositories/snapshots/log4j/apache-log4j-extras/1.2.17-SNAPSHOT/ Most important I fixed the duplicate classes issue. Maybe Jess, if you are reading this, ca

[jira] [Comment Edited] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659317#comment-13659317 ] Ralph Goers edited comment on LOG4J2-255 at 5/16/13 7:07 AM: -

[jira] [Commented] (LOG4J2-255) Multi-byte character strings are scrambled in log output

2013-05-16 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659317#comment-13659317 ] Ralph Goers commented on LOG4J2-255: Gary, that is absolutely incorrect. If I specify