Return-Path: 
 <dev-return-20273-apmail-avalon-dev-archive=avalon.apache.org@avalon.apache.org>
Delivered-To: apmail-avalon-dev-archive@avalon.apache.org
Received: (qmail 32750 invoked by uid 500); 16 Mar 2003 21:06:36 -0000
Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@avalon.apache.org>
List-Subscribe: <mailto:dev-subscribe@avalon.apache.org>
List-Help: <mailto:dev-help@avalon.apache.org>
List-Post: <mailto:dev@avalon.apache.org>
List-Id: "Avalon Developers List" <dev.avalon.apache.org>
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Delivered-To: mailing list dev@avalon.apache.org
Received: (qmail 32727 invoked from network); 16 Mar 2003 21:06:36 -0000
Received: from unknown (HELO wahoo) (65.196.130.133)
  by daedalus.apache.org with SMTP; 16 Mar 2003 21:06:36 -0000
Received: from meatloaf.fotap.org ([66.93.248.91] helo=apache.org)
	by wahoo with asmtp (Exim 3.35 #1 (Debian))
	id 18ufL6-0001eE-00
	for <dev@avalon.apache.org>; Sun, 16 Mar 2003 16:06:40 -0500
Date: Sun, 16 Mar 2003 16:06:36 -0500
Subject: Re: [phoenix] excalibur-logger jar in container lib directory
Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
From: Peter Royal <proyal@apache.org>
To: "Avalon Developers List" <dev@avalon.apache.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <200303161315.18190.peter@realityforge.org>
Message-Id: <2CB213BE-57F3-11D7-89AD-000393B61B56@apache.org>
X-Mailer: Apple Mail (2.551)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

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 -> proyal@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org