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.
-chris
Rob Leland wrote:
Looking at the gump output at : http://cvs.apache.org/builds/gump/latest/jakarta-struts.html
Gump is definately building with an old version of the struts build.xml file.
Notice the targets:
When gump executes the 'dist' target we get:
init:
[echo] --------- jakarta-struts 1.1-rc2 ---------
prepare.dist
prepare.library:
is printed out.
when I do a 'ant dist' from a clean state I get, and should get :
dist.legacy: init: [echo] ---------- Struts Legacy Distribution 1.1-rc2 ---------- prepare: resources: compile: docs: init: [echo] --------- jakarta-struts 1.1-rc2 ---------
I get the same results even if the directory isn't clean.
I thought gump started from a clean CVS checkout each time ? Or at least from an updated CVS !!!
Note that struts build.xml last changed June 19th.
-Rob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
