logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: Problem with Gump on 23/11
Date Sun, 24 Nov 2002 15:15:28 GMT


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" <vmassol@octo.com> wrote in message 
>FYI, Gump log4j build had some issue yesterday:
>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.


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

View raw message