You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by "Xu, William" <wx...@sprintspectrum.com> on 2002/05/29 00:17:25 UTC
RE: Log4j-1.2.3 - incorrect build ?
Thanks Ceki. The error was from command line compiling. I found out one of
our internal framework jars had log4j-1.1.3 included which I overlooked. So
now the problem is solved.
Regards,
William Xu
-----Original Message-----
From: Ceki Gülcü [mailto:ceki@qos.ch]
Sent: Tuesday, May 28, 2002 4:45 PM
To: Log4J Users List
Subject: Re: Log4j-1.2.3 - incorrect build?
Hmm, are you using JBuilder? If you are, then clean up classes from
earlier builds and start over. It appears that you suffer from a
compile time inconsistency and I assure you that log4j builds without
compile time errors.
At 13:03 28.05.2002 -0500, Xu, William wrote:
>All,
>
>One of my classes extends Filter. When I compile it, I received the
>following error message:
>
>MetricsLoggerFilter.java:25:
>com.spcs.premiere.common.framework.log.MetricsLogge
>rFilter should be declared abstract; it does not define
>setOption(java.lang.Stri
>ng,java.lang.String) in org.apache.log4j.spi.Filter
>public class MetricsLoggerFilter extends Filter
> ^
>MetricsLoggerFilter.java:193: getOptionStrings() in
>com.spcs.premiere.common.fra
>mework.log.MetricsLoggerFilter cannot override getOptionStrings() in
>org.apache.
>log4j.spi.Filter; attempting to assign weaker access privileges; was public
> private String[] getOptionStrings()
>
>
>The Filter class in 1.2.3 release (what I am using) does not have the
>getOptionStrings() method. Can somebody check if the log4j-1.2.3 (nt
>version0 was incorrectly built or I am missing something here?
>
>Regards,
>
>William Xu
--
Ceki
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>