Rob Leland wrote:Christopher Lenz wrote:
Hi Rob,
I would *strongly* doubt Gump using anything out-of-date in the build.
If I understand this correctly, you have changed the Struts build file on Jun 19 to remove the 'dist.legacy' target, commit message was
"Roll back changes so that inorder to build struts, a user must first go to the contrib.struts-legacy directory and do a seperate build..." [http://cvs.apache.org/viewcvs.cgi/jakarta-struts/build.xml]
So maybe you're not using the latest and greatest? ;-)
I am. I modified the build.xml last night to change the version that was echoed
out from 1.1-rc2 to 1.1-rc2-post. However, the string '1.1-rc2' was echoed
out and not '1.1-rc2-post'. I made this change about 4 hours before the attemped
build so gump should have picked up this change.
That must have been too late for last night's build. Note that the CVS updates are usually done several hours before the build starts, mainly because some CVS servers timeout etc.
Anyway, you can always see what has been updated by Gump on the CVS log page:
http://cvs.apache.org/builds/gump/latest/cvs_jakarta-struts.html
There is no update here, obviously.
You should also find the other Gump machines useful when dealing with such problems. The following one has picked up the change:
http://gump.cocoondev.org/jakarta-struts.html
Apparently the CVS update was done about 1 hour later.
Oops, forget that, it wasn't picked up there either. My eyes must be tricking me :-P
Here's something now: http://nagoya.apache.org/~rubys/gump/cvs_jakarta-struts.html
But still some time until the build starts...
-chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
