Vincent,
Thank you for letting us know. I seems that the "jakarta-site2" property was not set in the failed gump run.
It is usually set as jakarta-site2=../jakarta-site2 in the build.properties file. Up until now, gump was able to successfully deal with this issue. I do not see how the recent changes in the log4j build.xml file could result in the outcome you mention. Could it be due to Sam's recent changes in gump related to log4j?
"Vincent Massol" <[EMAIL PROTECTED]> wrote in message news:<000301c293bd$5db091f0$0200a8c0@octovma>...
Hi, FYI, Gump log4j build had some issue yesterday: http://cvs.apache.org/builds/gump/latest/jakarta-log4j.html Excerpt: Buildfile: build.xml Caught exception (org.apache.tools.ant.BuildException) while expanding site2.classpath: /home/rubys/jakarta/jakarta-log4j/${jakarta-site2}/lib not found. The build says "successful" but the jars that the log4j build generates were not created, which caused Gump to report a PREREQ failure for all other builds depending on log4j. Thanks -Vincent
-- Ceki
TCP implementations will follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. -- Jon Postel, RFC 793 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
