log4j-core jar doesn't have the socket classes.  the log4j-optional jar needs 
added to the classpath.

also need log4j-oro and log4j-xml in the classpath as well.

Thanks for the help, Curt

Scott


-----Original Message-----
From:   Curt Arnold [mailto:[EMAIL PROTECTED]
Sent:   Fri 2/25/2005 11:14 PM
To:     Log4J Developers List
Cc:     
Subject:        Re: [EMAIL PROTECTED]: Project logging-log4j-chainsaw (in 
module logging-chainsaw) failed
I'm not sure if we are looking at the same run since the Gump message  
seemed to arrive about an hour after your message.

Looking at  
http://brutus.apache.org/gump/public/logging-chainsaw/logging-log4j- 
chainsaw/gump_work/build_logging-chainsaw_logging-log4j-chainsaw.html

I added commons-vfs to the dependency list and it appears to show up in  
the classpath along with log4j.  The messages aren't consistent with a  
missing log4j.jar since they say that TTCCLayout is deprecated.  If  
log4j wasn't present, they would say that it could not be resolved.   
Before I added commons-vfs to the dependency, the build script gave a  
warning that it should be included.  Now it says that VFS is present.

I downloaded the Gump log4j.jar and it does not contain  
SocketHubAppender.class.  I don't know why, but will look at tomorrow.   
The unresolved getLogger() in the VFSLogFilePatternReceiver smells like  
a real issue.  Prior to today the VFS related classes were being built  
by Gump since VFS wasn't in the dependency list.



On Feb 25, 2005, at 9:37 PM, Paul Smith wrote:

> Ok. I've got the gump module out and now at least understand a bit  
> more about gump.
>
> The reason I think this failed is because the current Chainsaw build  
> expects a set of jars to be available as part of the compile  
> classpath.  I see that the gump descriptor has logging-log4j and  
> commons-vfs, but it is plain to see from below that these don't get  
> added to the compile classpath.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




<<winmail.dat>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to