I think I got this. Gump had the wrong location for the classes dir (now in
dist/classes instead of classes).
We'll see how gump acts after this.
-Mark
----- Original Message -----
From: "Curt Arnold" <[EMAIL PROTECTED]>
To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Sent: Thursday, January 05, 2006 12:18 PM
Subject: Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module
logging-log4j) failed
On Jan 5, 2006, at 11:47 AM, Mark Womack wrote:
I'll take a look at this tonight if no one gets a chance before then.
Not sure what is up, but might be related to my recent build changes?
I did not get this error when I ran the tests with my build changes,
so it has me a bit confused.
-Mark
I think the Gump failure is likely related to the recent build changes.
However, I think it only caused an existing problem to surface since I
had seen the tests/build.xml produce the same errors when not all jars
had been built previously. I'll take a look at it this afternoon.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
