[logback-user] Config file failures unexplained in list or JIRA

RobOaks roboaks at comcast.net
Thu Nov 29 13:43:32 CET 2012

Thanks so much for your detailed response Tony. Fortunately, I think it was
indeed mostly me :-). 

I am using Logback in the context of Talend, an ETL platform that is built
on Eclipse. Perhaps there were some Talend references to older Logback JARs
or something because once I fiddled around with classpath relates settings,
the config file parsing errors went away. The one thing that still doesn't
work is ANSI highlighting in the Talend (Eclipse) studio. However, I think
this is explained by

tony19 wrote:
> On Fri, Nov 23, 2012 at 7:41 AM, RobOaks <roboaks at comcast.net> wrote:
>> I am encountering several initialization errors with the logback.xml file
>> (below) that do not seem to be addressed in either this mailing list or
>> JIRA. I am running Logback 1.0.7 with SLF4J 1.7.2.
>> During initialization I receive the following Logback errors:
>> 1. No applicable action for [outputPatternAsHeader]. Try as I might, I
>> can
>> not get Logback to recognize this property.
> Double-check your classpath. It might be pointing to a version of logback
> that's older than 1.0.3 (where <outputPatternAsHeader> was introduced).
> [1]
> 2. No applicable action for [immediateFlush]. This error may be expected,
> as
>> I was able to glean from the list and JIRA that this property has been
>> eliminated. Please confirm.
> No, <immediateFlush> is still a valid property for layout encoders in
> logback-1.0.7. [2]
> 3. no applicable action for [withJansi] / There is no conversion class
>> registered for composite conversion word [highlight]. I am including
>> jansi-1.8.jar in the classpath but, obviously, this wouldn’t even come
>> into
>> play if withJansi isn’t even recognized.
> I don't have a Windows machine handy at the moment, but I'm guessing it's
> the same issue mentioned previously (an old version of logback in your
> classpath).
>> 4. Could not find Janino library on the class path. Skipping conditional
>> processing. Both commons-compiler.jar and janino.jar 2.6.1 are on the
>> classpath. I understand that there are potential issues with the use of
>> conditional processing because of Janino and I’m wondering if I should
>> abandon this feature, though it makes the config file significantly more
>> elegant.
> To use Janino, you must include *two* relevant jars: janino.jar and
> commons-compiler.jar. [3]
> I just tried your logback configuration with logback-1.0.7 and Janino, and
> there were no config errors. It output correctly to the console (with the
> color codes), and it correctly wrote the pattern header to the log file at
> /tmp/its/Idcp.log. [4]
> I wrote a HelloWorld application (output via SLF4J) with Eclipse Juno on
> OSX Mountain Lion. I included the following jars:
>  * slf4j-api-1.7.2.jar
>  * logback-core-1.0.7.jar
>  * logback-classic-1.0.7.jar
>  * janino-commons-compiler-2.6.1.jar
>  * janino-2.6.1.jar
> [1]
> http://logback.qos.ch/apidocs/ch/qos/logback/core/pattern/PatternLayoutEncoderBase.html#setOutputPatternAsHeader(boolean)
> [2]
> http://logback.qos.ch/apidocs/ch/qos/logback/core/encoder/LayoutWrappingEncoder.html#setImmediateFlush(boolean)
> [3] http://logback.qos.ch/setup.html#janino
> [4] http://pastebin.com/ZJpdbf2c
> _______________________________________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://mailman.qos.ch/mailman/listinfo/logback-user

View this message in context: http://old.nabble.com/Config-file-failures-unexplained-in-list-or-JIRA-tp34713039p34737193.html
Sent from the Logback User mailing list archive at Nabble.com.

More information about the Logback-user mailing list