[jira] [Commented] (LOG4J2-728) Look for log4j2.xml in assets folder (or the application data) in an Android APK.

[ https://issues.apache.org/jira/browse/LOG4J2-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120843#comment-14120843 ] Matt Sicker commented on LOG4J2-728: I was originally thinking about 2.1 being a relea

Re: org.apache.logging.log4j.streams.util

I'm finding that there may be many different ways to expose this API better than with constructors, and it's tough to choose a proper way to do it. Each class can have its own builder (very repetitive; can't even abstract it due to method chaining), or what I'm thinking might be useful is a more ge

[jira] [Created] (LOG4J2-812) Blocking state: org.apache​.loggin.lo​g4j.core.p​attern.Dat​ePatternCo​nverter

Mohit Anchlia created LOG4J2-812: Summary: Blocking state: org.apache​.loggin.lo​g4j.core.p​attern.Dat​ePatternCo​nverter Key: LOG4J2-812 URL: https://issues.apache.org/jira/browse/LOG4J2-812 Project

Re: org.apache.logging.log4j.streams.util

Cool! I hope it's coming along nicely :-) Gary On Wed, Sep 3, 2014 at 3:16 PM, Matt Sicker wrote: > I'm working on the constructors thing. Make the API a bit nicer. > > > On 3 September 2014 12:19, Gary Gregory wrote: > >> Matt, feel free to whack on iostreams, I'm done in there for today. >>

Re: org.apache.logging.log4j.streams.util

I'm working on the constructors thing. Make the API a bit nicer. On 3 September 2014 12:19, Gary Gregory wrote: > Matt, feel free to whack on iostreams, I'm done in there for today. > > Gary > > > On Wed, Sep 3, 2014 at 12:13 PM, Matt Sicker wrote: > >> That's still a possibility, but I'm stil

Re: org.apache.logging.log4j.streams.util

Matt, feel free to whack on iostreams, I'm done in there for today. Gary On Wed, Sep 3, 2014 at 12:13 PM, Matt Sicker wrote: > That's still a possibility, but I'm still not sold on it. > > > On 3 September 2014 11:04, Gary Gregory wrote: > >> Then what about matching the module name? log4j-io

Re: log4j-streams and ExtendedLoggers

http://docs.oracle.com/javase/8/docs/api/javax/sql/CommonDataSource.html#setLogWriter-java.io.PrintWriter- > Messages printed to a data source- specific log writer are not printed to the log writer associated with the java.sql.DriverManager class. When a DataSource object is created the log writer

Re: Could we add a 2.2 release target on JIRA?

Thanks! On 3 September 2014 10:39, Gary Gregory wrote: > I added a 2.2. > > Gary > > > On Wed, Sep 3, 2014 at 9:16 AM, Matt Sicker wrote: > >> So we can start separating features based on 2.1 and 2.2. >> >> -- >> Matt Sicker >> > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org

Re: Confusing plugin manager output

That's from collectPlugins() I believe. There's a JIRA issue about slow start-up or something like that. It's definitely related. I believe we can get away with a single plugin scan followed by multiple lookups in the plugin registry. On 3 September 2014 11:15, Gary Gregory wrote: > I find this

[jira] [Updated] (LOG4J2-808) RegexFilter does not work properly with RollingFileAppenders

[ https://issues.apache.org/jira/browse/LOG4J2-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-808: --- Fix Version/s: (was: 2.0-rc1) > RegexFilter does not work properly with RollingFileAppenders > --

[jira] [Resolved] (LOG4J2-808) RegexFilter does not work properly with RollingFileAppenders

[ https://issues.apache.org/jira/browse/LOG4J2-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-808. Resolution: Not a Problem > RegexFilter does not work properly with RollingFileAppenders >

[jira] [Commented] (LOG4J2-808) RegexFilter does not work properly with RollingFileAppenders

[ https://issues.apache.org/jira/browse/LOG4J2-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120071#comment-14120071 ] Ralph Goers commented on LOG4J2-808: I am going to mark this as resolved since everyth

[jira] [Commented] (LOG4J2-808) RegexFilter does not work properly with RollingFileAppenders

[ https://issues.apache.org/jira/browse/LOG4J2-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120068#comment-14120068 ] Ralph Goers commented on LOG4J2-808: The part you seem to be missing is that filtering

[jira] [Commented] (LOG4J2-808) RegexFilter does not work properly with RollingFileAppenders

[ https://issues.apache.org/jira/browse/LOG4J2-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120027#comment-14120027 ] Pranav Pratap commented on LOG4J2-808: -- Thanks for your clarification. But you still

Confusing plugin manager output

I find this confusing: 2014-09-03 12:11:46,073 DEBUG Generated plugins in 0.155939 seconds, packages: [org.apache.logging.log4j.core, org.apache.logging.log4j.test], preload: false. 2014-09-03 12:11:46,209 DEBUG Generated plugins in 0.135048 seconds, packages: [org.apache.logging.log4j.core, org.a

Re: org.apache.logging.log4j.streams.util

That's still a possibility, but I'm still not sold on it. On 3 September 2014 11:04, Gary Gregory wrote: > Then what about matching the module name? log4j-io? > > Gary > > > On Wed, Sep 3, 2014 at 9:17 AM, Matt Sicker wrote: > >> I'll take a look at the constructors and such. I think this is a

Re: org.apache.logging.log4j.streams.util

Then what about matching the module name? log4j-io? Gary On Wed, Sep 3, 2014 at 9:17 AM, Matt Sicker wrote: > I'll take a look at the constructors and such. I think this is a prime > candidate for the builder pattern. > > Also, I renamed the o.a.l.l.streams package to o.a.l.l.io to match the >

Re: org.apache.logging.log4j.streams.util

Nevermind, I see it. Gary On Wed, Sep 3, 2014 at 11:58 AM, Gary Gregory wrote: > You must not have pushed that commit yet. > > Gary > > > On Wed, Sep 3, 2014 at 9:17 AM, Matt Sicker wrote: > >> I'll take a look at the constructors and such. I think this is a prime >> candidate for the builder

Re: org.apache.logging.log4j.streams.util

You must not have pushed that commit yet. Gary On Wed, Sep 3, 2014 at 9:17 AM, Matt Sicker wrote: > I'll take a look at the constructors and such. I think this is a prime > candidate for the builder pattern. > > Also, I renamed the o.a.l.l.streams package to o.a.l.l.io to match the > java.io p

[jira] [Comment Edited] (LOG4J2-808) RegexFilter does not work properly with RollingFileAppenders

[ https://issues.apache.org/jira/browse/LOG4J2-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119996#comment-14119996 ] Ralph Goers edited comment on LOG4J2-808 at 9/3/14 3:55 PM: Ex

[jira] [Comment Edited] (LOG4J2-728) Look for log4j2.xml in assets folder (or the application data) in an Android APK.

[ https://issues.apache.org/jira/browse/LOG4J2-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119998#comment-14119998 ] Gary Gregory edited comment on LOG4J2-728 at 9/3/14 3:54 PM: -

[jira] [Commented] (LOG4J2-728) Look for log4j2.xml in assets folder (or the application data) in an Android APK.

[ https://issues.apache.org/jira/browse/LOG4J2-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119998#comment-14119998 ] Gary Gregory commented on LOG4J2-728: - [~jvz] Is there a fix in git or are you saying

[jira] [Commented] (LOG4J2-808) RegexFilter does not work properly with RollingFileAppenders

[ https://issues.apache.org/jira/browse/LOG4J2-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119996#comment-14119996 ] Ralph Goers commented on LOG4J2-808: Expected Results: Case 1: You should only get ev

[jira] [Resolved] (LOG4J2-811) SimpleLogger throws ArrayIndexOutOfBoundsException for an empty array

[ https://issues.apache.org/jira/browse/LOG4J2-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-811. - Resolution: Fixed Somehow my previous edit to SimpleLogger is gone. Oh well, I have better tests

[jira] [Reopened] (LOG4J2-811) SimpleLogger throws ArrayIndexOutOfBoundsException for an empty array

[ https://issues.apache.org/jira/browse/LOG4J2-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-811: - Reopening for a commit. > SimpleLogger throws ArrayIndexOutOfBoundsException for an empty array > ---

Re: Could we add a 2.2 release target on JIRA?

I added a 2.2. Gary On Wed, Sep 3, 2014 at 9:16 AM, Matt Sicker wrote: > So we can start separating features based on 2.1 and 2.2. > > -- > Matt Sicker > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: log4j-streams and ExtendedLoggers

My understanding is that setting a PW on a DriverManager is for all of JDBC and any driver. Setting a PW on a DataSource is just for that one data source instance. Each driver may implement logging in any way of course, so there is no guarantee. Gary On Wed, Sep 3, 2014 at 9:08 AM, Matt Sicker

[jira] [Comment Edited] (LOG4J2-808) RegexFilter does not work properly with RollingFileAppenders

[ https://issues.apache.org/jira/browse/LOG4J2-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119972#comment-14119972 ] Pranav Pratap edited comment on LOG4J2-808 at 9/3/14 3:33 PM: --

[jira] [Commented] (LOG4J2-808) RegexFilter does not work properly with RollingFileAppenders

[ https://issues.apache.org/jira/browse/LOG4J2-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119972#comment-14119972 ] Pranav Pratap commented on LOG4J2-808: -- The reason I kept 2 appender's is I need to v

[jira] [Comment Edited] (LOG4J2-811) SimpleLogger throws ArrayIndexOutOfBoundsException for an empty array

[ https://issues.apache.org/jira/browse/LOG4J2-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119419#comment-14119419 ] Remko Popma edited comment on LOG4J2-811 at 9/3/14 11:54 AM: -

Re: org.apache.logging.log4j.streams.util

I'll take a look at the constructors and such. I think this is a prime candidate for the builder pattern. Also, I renamed the o.a.l.l.streams package to o.a.l.l.io to match the java.io package that this module emulates. I think it's a pretty neat package name now (especially with the foo.io domain

[jira] [Commented] (LOG4J2-728) Look for log4j2.xml in assets folder (or the application data) in an Android APK.

[ https://issues.apache.org/jira/browse/LOG4J2-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119857#comment-14119857 ] Nelson MELINA commented on LOG4J2-728: -- Ok, thanks [~jvz]. If there is help needed te

Could we add a 2.2 release target on JIRA?

So we can start separating features based on 2.1 and 2.2. -- Matt Sicker

Re: log4j-streams and ExtendedLoggers

One thing to note is that CommonDataSource takes a PrintWriter as well which says it's separate from the DriverManager log. If you look up a DataSource via JNDI and set a log writer, will that take effect everywhere? Or do you need to rebind it? On 3 September 2014 00:54, Gary Gregory wrote: >

Re: NoSQL 3rd party updates

I'll try to take a better look into this sometime this week. I'm pretty sure the JPA things should be good. I'll take a look at the unit tests for log4j-nosql a bit better to see if we can safely upgrade. On 2 September 2014 09:24, Matt Sicker wrote: > The JPA/EclipseLink update should be fine

Re: git commit: Move longish comment before code.

I just noticed, but we should not convert Messages to strings to make async loggers work. (This wastes CPU if the level is too low and the message doesn't get logged.) I wonder if there are other placed where this is happening. Sent from my iPhone > On 2014/09/02, at 22:45, ggreg...@apache.or