You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Rob Leland <rl...@apache.org> on 2003/06/24 03:49:56 UTC
Gump using old ant build file.
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
Stale Gumps (was RE: Gump using old ant build file.)
Posted by Adam Jack <aj...@TrySybase.com>.
On Tuesday 24 June 2003 03:22, Christopher Lenz wrote:
> I would *strongly* doubt Gump using anything out-of-date in the build.
Actually, look here, it *is* using out of date stuff:
-----------------------------------------------------------------------
http://cvs.apache.org/builds/gump/latest/cvs_krysalis-version.html
cvs -z3 -d
:pserver:anonymous@cvs.metamorphosis.sourceforge.net:/cvsroot/metamorphosis
update -P -d -A krysalis-version
cvs [update aborted]: recv() from server cvs.metamorphosis.sourceforge.net:
EOF
cvs server: Updating krysalis-version
...
/home/rubys/bin/timeout: timed out
cvs [update aborted]: received termination signal
-----------------------------------------------------------------------
SourceForge have knobbled their CVS server against such accesses (in the
name of making developer lives easier) and much as this is an SF.net user
woe, two things:
1) Even if/when gump detects that CVS fails it only seems to mark the CVS
index in red, it doesn't mark the main build dashboard in red. As such, such
failures can go unnoticed.
http://cvs.apache.org/builds/gump/latest/cvs_index.html krysalis-version =
FAILED
http://cvs.apache.org/builds/gump/latest/index.html krysalis-version =
SUCCESS.
2) The reason the build dashboard isn't in red is that Gump doesn't (it
seems to me) clean out it's CVS area each time, so it has a "stale" copy of
the code with which to "update" the build area and with which to build.
FWIIW:
3) Gump doesn't seem to clean out it's work area each time, which can be
confusing when profiles change and projects get renamed or go away.
This is one of the things I mean to log in the bug tracker, now Sam's
created it.
BTW: I suspect a fix might be in adding to the gump.sh script that Sam
wrote, and Nick Chalko and I built upon. Not elegant (yet another language
in the mix, and no PC version) but easiest...
P.S. SF.net doing this truly sucks for gumping. I have no fix for that...
regards
Adam
Re: Gump using old ant build file.
Posted by James Mitchell <jm...@apache.org>.
On Tuesday 24 June 2003 03:22, 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 rolled my local build.xml back to 1.107 and referenced the legacy.jar as
"contrib/......" instead of "../contrib/......" and all builds fine for me.
>
> -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
--
James Mitchell
Software Developer/Struts Evangelist
http://www.struts-atlanta.org
770-822-3359
AIM:jmitchtx
Re: Gump using old ant build file.
Posted by Christopher Lenz <cm...@gmx.de>.
Christopher Lenz wrote:
> 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
Re: Gump using old ant build file.
Posted by Christopher Lenz <cm...@gmx.de>.
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.
Did you read the other comment I wrote? The Struts build.xml in CVS HEAD
doesn't even contain a 'dist.legacy' target (AFAICT), so how should that
have been run?
-chris
[Very very often it is a big waste of time to suspect an error in the system
before thinking that oneself might be doing something wrong ;-) ]
>> 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
Re: Gump using old ant build file.
Posted by Rob Leland <rl...@apache.org>.
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.
>
>
> -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
>
>
Re: Gump using old ant build file.
Posted by Christopher Lenz <cm...@gmx.de>.
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? ;-)
-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
--
Christopher Lenz
/=/ cmlenz at gmx.de
RE: [PATCH] Profile.dtd
Posted by Danny Angus <da...@apache.org>.
done.
> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@apache.org]
> Sent: 24 June 2003 12:03
> To: gump@jakarta.apache.org
> Subject: Re: [PATCH] Profile.dtd
>
>
> On Tue, 24 Jun 2003, Danny Angus <da...@apache.org> wrote:
>
> > (PS patch is simply appended, if you want some other submission let
> > me know)
>
> Yep, go ahead and commit it yourself ;-)
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gump-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: gump-help@jakarta.apache.org
>
Re: [PATCH] Profile.dtd
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 24 Jun 2003, Danny Angus <da...@apache.org> wrote:
> (PS patch is simply appended, if you want some other submission let
> me know)
Yep, go ahead and commit it yourself ;-)
Stefan
[PATCH] Profile.dtd
Posted by Danny Angus <da...@apache.org>.
Hi,
profile.xml, and other profile files, contain modules, projects, repositories and servers.
This patch extends the profile DTD to validate accordingly.
Reason: because newbies like me can use DTD's to validate our xml before we fire up GUMP
d.
(PS patch is simply appended, if you want some other submission let me know)
cvs -z9 diff -u dtd/profile.dtd
Index: dtd/profile.dtd
===================================================================
RCS file: /home/cvs/jakarta-gump/dtd/profile.dtd,v
retrieving revision 1.1
diff -u -r1.1 profile.dtd
--- dtd/profile.dtd 26 Aug 2001 23:01:46 -0000 1.1
+++ dtd/profile.dtd 24 Jun 2003 10:52:04 -0000
@@ -1,10 +1,23 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
+<!ELEMENT profile (module|project|repository|server)*>
+<!ELEMENT module EMPTY>
+<!ELEMENT project EMPTY>
+<!ELEMENT repository EMPTY>
+<!ELEMENT server EMPTY>
-<!ELEMENT profile (project*) >
-<!ELEMENT project EMPTY >
-
-<!ATTLIST profile
- name CDATA #IMPLIED >
-
+<!ATTLIST profile
+ name CDATA #IMPLIED
+>
+<!ATTLIST module
+ href CDATA #REQUIRED
+>
<!ATTLIST project
- href CDATA #REQUIRED >
+ href CDATA #REQUIRED
+>
+<!ATTLIST repository
+ href CDATA #REQUIRED
+>
+<!ATTLIST server
+ href CDATA #REQUIRED
+>
+
Re: Gump using old ant build file.
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 23 Jun 2003, Rob Leland <rl...@apache.org> wrote:
> I should have added that the struts build.xml file uses an <ant >
> target, to call another build file first.
No real problem, many other build files do so as well.
What you probably need is an additional <work> to point to the
compiled classes of that "subbuild" in order to get them on the
classpath (if you need them during later compilations or tests, that
is).
Or you can do it correctly, see below 8-)
> I had originally tried to define a second project but wasn't
> sucessfull in telling the struts-core that it's dependancy on
> struts-legacy.jar could be satisfied from the previously built
> project.
What has been the problem?
Christopher Lenz has explained on struts-dev what would have been the
correct approach IMHO. Create two <project>s in the Struts Gump
descriptor, one for -legacy and make jakarta-struts depend on -legacy.
Stefan
Re: Gump using old ant build file.
Posted by Rob Leland <rl...@apache.org>.
I should have added that the struts build.xml file uses an <ant > target,
to call another build file first. I had originally tried to define a second
project but wasn't sucessfull in telling the struts-core that it's
dependancy
on struts-legacy.jar could be satisfied from the previously built project.
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: gump-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: gump-help@jakarta.apache.org
>
>
>