RE: configuring a non-core appender in log4j2

2014-03-28 Thread Zabicki Roman (HERE/Chicago)
That did the trick. Thank you for your help. -Original Message- From: Zabicki Roman (HERE/Chicago) Sent: Friday, March 21, 2014 5:25 PM To: Log4J Users List Subject: RE: configuring a non-core appender in log4j2 when I build -- you've described the problem exactly. I'm building

Re: configuring a non-core appender in log4j2

2014-03-22 Thread Ralph Goers
that page before, but I didn't get it. -Original Message- From: Ralph Goers [mailto:ralph.go...@dslextreme.com] Sent: Friday, March 21, 2014 3:56 PM To: Log4J Users List Subject: Re: configuring a non-core appender in log4j2 If the log4j flume jar is in the class path it should

Re: configuring a non-core appender in log4j2

2014-03-21 Thread Ralph Goers
If the log4j flume jar is in the class path it should automatically be included as it has its own Log4j2Plugin.dat file. However, you can always manually cause plugins to be located by specifying the packages attribute - see http://logging.apache.org/log4j/2.x/manual/configuration.html#XML.

RE: configuring a non-core appender in log4j2

2014-03-21 Thread Zabicki Roman (HERE/Chicago)
, March 21, 2014 3:56 PM To: Log4J Users List Subject: Re: configuring a non-core appender in log4j2 If the log4j flume jar is in the class path it should automatically be included as it has its own Log4j2Plugin.dat file. However, you can always manually cause plugins to be located by specifying