I don't see my change to tests/build.xml in the list of workspace modifications at http://brutus.apache.org/gump/public/logging-log4j/gump_file/ changes_to_logging-log4j.txt.html. So I'm assuming that the change didn't propagate to the anonymous CVS in time for that Gump run and the build failure for logging-log4j-tests will clear up on the next iteration.


On Feb 22, 2005, at 10:32 AM, Curt Arnold wrote:

I committed a change to tests/build.xml that fixed the issue on my machine. The commit time was several hours prior to the Gump run and my log4cxx commits at approximately the same time fixed the log4cxx build issues. I thought there used to be a way to see the CVS changes in the Gump results, but I couldn't find them in the output.


--------------------------------------------------------------------- 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]



Reply via email to