Sean Lagassick wrote:
>
> that's the problem with GUMP - it tests us against the bleeding
> edge. Log4J has just changed in CVS, such that FileAppender can't
> be used for writing out to the console anymore, and a
> ConsoleAppender has been added for this purpose.
No question that this isn't Turbine's fault.
Without gump, how long would this incompatibility gone unnoticed?
There undoubtably are other projects out there using log4j. If each binds
to a specific release and there isn't a period of deprecation, which
version of the jar file do you put first in your classpath?
The owner of the log4j project has been notified. At least twice - once by
me and once by Jon.
Still consider this a problem with Gump? ;-)
- Sam Ruby
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
