logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Deboy" <sde...@comotivsystems.com>
Subject RE: [GUMP@brutus]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed
Date Sat, 26 Feb 2005 07:21:06 GMT
log4j-core jar doesn't have the socket classes.  the log4j-optional jar needs added to the

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

Thanks for the help, Curt


-----Original Message-----
From:	Curt Arnold [mailto:carnold@apache.org]
Sent:	Fri 2/25/2005 11:14 PM
To:	Log4J Developers List
Subject:	Re: [GUMP@brutus]: 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  

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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message