Re: org.apache.logging.log4j.core.config.plugins.PluginAttribute.required()

2014-07-08 Thread Ralph Goers
IMO the proper, and recommended, way to do programmatic configuration is to implement a Configuration, the end result of which is a tree of Nodes. Doing that leverages everything we have to offer and is probably simpler to implement in the end. We should create a sample that shows how to do th

Re: org.apache.logging.log4j.core.config.plugins.PluginAttribute.required()

2014-07-08 Thread Gary Gregory
Actually, if the framework detects a "required" violation and logs a message, it should not call the create() method, so there would no double logging. It would then be up to the plugin author to decide what level of validation he or she wants: - Use the required annotation attribute and let the

Re: org.apache.logging.log4j.core.config.plugins.PluginAttribute.required()

2014-07-08 Thread Ralph Goers
That is why programs that do programmatic configuration should use an API and not call the components directly Sent from my iPad > On Jul 8, 2014, at 6:56 PM, Gary Gregory wrote: > > Hm... if the error logging takes place in the plugin framework, then it > should be removed from the create()

Re: org.apache.logging.log4j.core.config.plugins.PluginAttribute.required()

2014-07-08 Thread Matt Sicker
Crap, that does actually make things more complicated! It's almost getting to the point where bytecode manipulation is starting to sound like a decent idea at times. On 8 July 2014 20:56, Gary Gregory wrote: > Hm... if the error logging takes place in the plugin framework, then it > should be r

Re: org.apache.logging.log4j.core.config.plugins.PluginAttribute.required()

2014-07-08 Thread Gary Gregory
Hm... if the error logging takes place in the plugin framework, then it should be removed from the create() methods, but then apps that do programmatic configuration will not benefit from the error logging. We would then need to either keep the current guard clauses (with no logging) or remove the

Re: Config element name confusion

2014-07-08 Thread Gary Gregory
On Tue, Jul 8, 2014 at 11:18 AM, Ralph Goers wrote: > > On Jul 8, 2014, at 7:49 AM, Gary Gregory wrote: > > On Tue, Jul 8, 2014 at 10:47 AM, Ralph Goers > wrote: > >> >> On Jul 8, 2014, at 7:32 AM, Gary Gregory wrote: >> >> On Mon, Jul 7, 2014 at 1:44 PM, Ralph Goers >> wrote: >> >>> Well, If

[jira] [Closed] (LOG4J2-695) Custom Logger with restrictions on existing methods

2014-07-08 Thread SIBISH BASHEER (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SIBISH BASHEER closed LOG4J2-695. - log4j2 Custom Logger is working as expected with generated logs in Splunk CIM standard. > Custom Lo

[jira] [Commented] (LOG4J2-695) Custom Logger with restrictions on existing methods

2014-07-08 Thread SIBISH BASHEER (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055722#comment-14055722 ] SIBISH BASHEER commented on LOG4J2-695: --- I agree, the machine might have some other

[jira] [Comment Edited] (LOG4J2-695) Custom Logger with restrictions on existing methods

2014-07-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055654#comment-14055654 ] Remko Popma edited comment on LOG4J2-695 at 7/9/14 12:43 AM: -

[jira] [Comment Edited] (LOG4J2-695) Custom Logger with restrictions on existing methods

2014-07-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055654#comment-14055654 ] Remko Popma edited comment on LOG4J2-695 at 7/9/14 12:40 AM: -

[jira] [Comment Edited] (LOG4J2-551) TimeBasedTriggeringPolicy is not triggering file roll-over

2014-07-08 Thread Bohdan Mushkevych (JIRA)
ance, *filePattern*: {code} filePattern="${log.path}/$${date:MMdd}{GMT+0}/%d{MMddHH}{GMT+0}-${sd:type}-${hostName}.%i.log.gz"{code} produces folders with such names as: *20140708\{GMT+0\}*. How could I instruct {code}$${date:MMdd}{code} in filePattern to use UTC time zone?

[jira] [Assigned] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-704: -- Assignee: Remko Popma > -Dlog4j.configurationFile no longer accepts relative paths > --

[jira] [Assigned] (LOG4J2-519) Custom/Extended Loggers

2014-07-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-519: -- Assignee: Remko Popma > Custom/Extended Loggers > --- > > K

[jira] [Comment Edited] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055658#comment-14055658 ] Remko Popma edited comment on LOG4J2-704 at 7/8/14 11:22 PM: -

[jira] [Commented] (LOG4J2-519) Custom/Extended Loggers

2014-07-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055663#comment-14055663 ] Remko Popma commented on LOG4J2-519: Tool to be added to the {{org.apache.logging.log4

[jira] [Commented] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055658#comment-14055658 ] Remko Popma commented on LOG4J2-704: This may be related to the changes I made for LOG

[jira] [Commented] (LOG4J2-695) Custom Logger with restrictions on existing methods

2014-07-08 Thread SIBISH BASHEER (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055651#comment-14055651 ] SIBISH BASHEER commented on LOG4J2-695: --- java -jar microbenchmarks.jar -f 5 -wi 10 -

[jira] [Commented] (LOG4J2-695) Custom Logger with restrictions on existing methods

2014-07-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055654#comment-14055654 ] Remko Popma commented on LOG4J2-695: Thanks for confirming the configuration. With mul

[jira] [Comment Edited] (LOG4J2-666) Ability to use a custom MBean domain

2014-07-08 Thread Te L (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055575#comment-14055575 ] Te L edited comment on LOG4J2-666 at 7/8/14 10:51 PM: -- "ConfigLocatio

[jira] [Comment Edited] (LOG4J2-666) Ability to use a custom MBean domain

2014-07-08 Thread Te L (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055575#comment-14055575 ] Te L edited comment on LOG4J2-666 at 7/8/14 10:50 PM: -- "ConfigLocatio

[jira] [Commented] (LOG4J2-666) Ability to use a custom MBean domain

2014-07-08 Thread Te L (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055575#comment-14055575 ] Te L commented on LOG4J2-666: - "ConfigLocationUri" is an attribute of the log4j2 MBean. It's g

[jira] [Commented] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055570#comment-14055570 ] Ralph Goers commented on LOG4J2-704: Is this a standalone app or in a web container?

[jira] [Commented] (LOG4J2-703) Log4J 2 on Android : Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

2014-07-08 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055565#comment-14055565 ] Ralph Goers commented on LOG4J2-703: To my knowledge no one has ever tested on Android

[jira] [Commented] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Andy Grove (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055510#comment-14055510 ] Andy Grove commented on LOG4J2-704: --- You are correct. This must have been from when I tr

[jira] [Updated] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Andy Grove (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Grove updated LOG4J2-704: -- Description: I just upgraded from beta9 to rc2 and my command line applications now fail on startup.

[jira] [Commented] (LOG4J2-703) Log4J 2 on Android : Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

2014-07-08 Thread Matt Sicker (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055487#comment-14055487 ] Matt Sicker commented on LOG4J2-703: It appears that Android does not ship with the {{

Re: org.apache.logging.log4j.core.config.plugins.PluginAttribute.sensitive()

2014-07-08 Thread Matt Sicker
Or even hideInLogs On 8 July 2014 09:27, Gary Gregory wrote: > What about "hide"? > > Gary > > > On Mon, Jul 7, 2014 at 7:32 PM, Remko Popma wrote: > >> What about "masked" or "shouldBeMasked"? >> >> Sent from my iPhone >> >> On 2014/07/08, at 7:58, Matt Sicker wrote: >> >> Well, it's more li

[jira] [Commented] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055391#comment-14055391 ] Gary Gregory commented on LOG4J2-704: - That does NOT look like a 2.0-rc2 stack trace.

[jira] [Issue Comment Deleted] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-704: Comment: was deleted (was: That does NOT look like a 2.0-rc2 stack trace. {{ConfigurationFactory.

[jira] [Commented] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055390#comment-14055390 ] Gary Gregory commented on LOG4J2-704: - That does NOT look like a 2.0-rc2 stack trace.

[jira] [Updated] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Andy Grove (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Grove updated LOG4J2-704: -- Description: I just upgraded from beta9 to rc2 and my command line applications now fail on startup.

[jira] [Created] (LOG4J2-704) -Dlog4j.configurationFile no longer accepts relative paths

2014-07-08 Thread Andy Grove (JIRA)
Andy Grove created LOG4J2-704: - Summary: -Dlog4j.configurationFile no longer accepts relative paths Key: LOG4J2-704 URL: https://issues.apache.org/jira/browse/LOG4J2-704 Project: Log4j 2 Issue Ty

[jira] [Commented] (LOG4J2-551) TimeBasedTriggeringPolicy is not triggering file roll-over

2014-07-08 Thread Bohdan Mushkevych (JIRA)
%i.log.gz"{code} produces folders with such names as: *20140708\{GMT+0\}*. How could I instruct {code}$${date:MMdd}{code} in filePattern to use UTC time zone? > TimeBasedTriggeringPolicy is not triggeri

[jira] [Commented] (LOG4J2-695) Custom Logger with restrictions on existing methods

2014-07-08 Thread SIBISH BASHEER (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055139#comment-14055139 ] SIBISH BASHEER commented on LOG4J2-695: --- Yes Remko, did not modify anything and they

[jira] [Comment Edited] (LOG4J2-695) Custom Logger with restrictions on existing methods

2014-07-08 Thread SIBISH BASHEER (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055139#comment-14055139 ] SIBISH BASHEER edited comment on LOG4J2-695 at 7/8/14 5:07 PM: -

Re: custom loggers

2014-07-08 Thread Remko Popma
Ok, thanks for the confirm! Sent from my iPhone > On 2014/07/09, at 1:41, Gary Gregory wrote: > >> On Tue, Jul 8, 2014 at 11:33 AM, Remko Popma wrote: >> All right then, I'll add it to the core module. >> Package name "org.apache.logging.log4j.core.tools" ? > > Seems OK to me. > > Gary >>

Re: custom loggers

2014-07-08 Thread Gary Gregory
On Tue, Jul 8, 2014 at 11:33 AM, Remko Popma wrote: > All right then, I'll add it to the core module. > Package name "org.apache.logging.log4j.core.tools" ? > Seems OK to me. Gary > > > On Mon, Jul 7, 2014 at 11:44 PM, Gary Gregory > wrote: > >> Well, yes, but it feels wrong to fatten up the

Re: custom loggers

2014-07-08 Thread Remko Popma
All right then, I'll add it to the core module. Package name "org.apache.logging.log4j.core.tools" ? On Mon, Jul 7, 2014 at 11:44 PM, Gary Gregory wrote: > Well, yes, but it feels wrong to fatten up the API jar with tooling. I > could see adding it in core though, maybe. > > Gary > > > On Mon,

Re: Config element name confusion

2014-07-08 Thread Ralph Goers
On Jul 8, 2014, at 7:49 AM, Gary Gregory wrote: > On Tue, Jul 8, 2014 at 10:47 AM, Ralph Goers > wrote: > > On Jul 8, 2014, at 7:32 AM, Gary Gregory wrote: > >> On Mon, Jul 7, 2014 at 1:44 PM, Ralph Goers >> wrote: >> Well, If there is only one Filter then it would just be declared. If th

Re: Config element name confusion

2014-07-08 Thread Gary Gregory
On Tue, Jul 8, 2014 at 10:47 AM, Ralph Goers wrote: > > On Jul 8, 2014, at 7:32 AM, Gary Gregory wrote: > > On Mon, Jul 7, 2014 at 1:44 PM, Ralph Goers > wrote: > >> Well, If there is only one Filter then it would just be declared. If >> there is more than one then it should be: >> >> >> … >

Re: Config element name confusion

2014-07-08 Thread Ralph Goers
On Jul 8, 2014, at 7:32 AM, Gary Gregory wrote: > On Mon, Jul 7, 2014 at 1:44 PM, Ralph Goers > wrote: > Well, If there is only one Filter then it would just be declared. If there is > more than one then it should be: > > > … > … > > > Even in this case since there is only the Composi

Re: Config element name confusion

2014-07-08 Thread Gary Gregory
On Mon, Jul 7, 2014 at 1:44 PM, Ralph Goers wrote: > Well, If there is only one Filter then it would just be declared. If there > is more than one then it should be: > > > … > … > > > Even in this case since there is only the CompositeFilter (which contains > the other Filters) there should

Re: org.apache.logging.log4j.core.config.plugins.PluginAttribute.sensitive()

2014-07-08 Thread Gary Gregory
What about "hide"? Gary On Mon, Jul 7, 2014 at 7:32 PM, Remko Popma wrote: > What about "masked" or "shouldBeMasked"? > > Sent from my iPhone > > On 2014/07/08, at 7:58, Matt Sicker wrote: > > Well, it's more like an "isPassword" boolean, really. Like, should this > attribute be masked or has

[jira] [Updated] (LOG4J2-703) Log4J 2 on Android : Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

2014-07-08 Thread Nelson MELINA (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nelson MELINA updated LOG4J2-703: - Summary: Log4J 2 on Android : Could not find class 'javax.naming.InitialContext', referenced from

[jira] [Updated] (LOG4J2-703) Log4J2 on Android : Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

2014-07-08 Thread Nelson MELINA (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nelson MELINA updated LOG4J2-703: - Description: Hi guys, i'm trying to use Log4J2 in an Android (19) application and it's not worki

[jira] [Updated] (LOG4J2-703) Log4J2 on Android : Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

2014-07-08 Thread Nelson MELINA (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nelson MELINA updated LOG4J2-703: - Description: Hi guys, i'm trying to use Log4J2 in an Android (19) application and it's not worki

[jira] [Updated] (LOG4J2-703) Log4J2 on Android : Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

2014-07-08 Thread Nelson MELINA (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nelson MELINA updated LOG4J2-703: - Description: Hi guys, i'm trying to use Log4J2 in an Android (19) application and it's not worki

[jira] [Created] (LOG4J2-703) Log4J2 on Android : Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

2014-07-08 Thread Nelson MELINA (JIRA)
Nelson MELINA created LOG4J2-703: Summary: Log4J2 on Android : Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup Key: LOG4J2-703 URL

[jira] [Updated] (LOG4J2-703) Log4J2 on Android : Could not find class 'javax.naming.InitialContext', referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup

2014-07-08 Thread Nelson MELINA (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nelson MELINA updated LOG4J2-703: - Description: Hi guys, i'm trying to use Log4J2 in an Android (19) application and it's not worki

[jira] [Comment Edited] (LOG4J2-660) RunLogback throws ClassCastException

2014-07-08 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054583#comment-14054583 ] Remko Popma edited comment on LOG4J2-660 at 7/8/14 7:45 AM: So