Re: [phoenix] excalibur-logger jar in container lib directory

On Saturday, March 15, 2003, at 09:15  PM, Peter Donald wrote:
> We previously enabled this so that users could define their own  
> targets.

at my request :) I'm not doing that anymore though.

> Anyways I just temporarily disabled this - see if that fixes your  
> problem.

Yes, it fixes it. The excalibur-logger-1.0.1 jar you have added does  
not have support for the SMTP target factories though. I am also unable  
to build a version of that jar with both SMTP *and* log4j support since  
something is wacky in my environment:

check-environment:

BUILD FAILED
java.lang.VerifyError: (class: org/apache/log4j/LogManager, method:  
<clinit> signature: ()V) Incompatible argument to function
         at java.lang.Class.getConstructors0(Native Method)
         at java.lang.Class.getDeclaredConstructors(Class.java:1072)
         at  
org.apache.tools.ant.AntClassLoader.initializeClass(AntClassLoader.java: 
479)
         at  
org.apache.tools.ant.taskdefs.Available.checkClass(Available.java:493)
         at  
org.apache.tools.ant.taskdefs.Available.eval(Available.java:295)
         at  
org.apache.tools.ant.taskdefs.Available.execute(Available.java:247)

>> view of the interface. If excalibur-logger was broked out into two
>> jars, one for interface one for impl, the interface jar could go into
>> the common classloader with the impl only in the container-private
>> classloader.
>
> That would be the eventual plan.

And that would fix application log targets. cool.

-pete

-- 
peter royal -> [email protected]