----- Original Message -----
From: "Sam Ruby" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 21, 2001 6:35 PM
Subject: Re: [gump][cactus] nightlies for Cactus-23
> Let me start with the original question:
> >
> > Could you set up Gump so that it copies the nightly build files to the
> > nightly area for cactus-23 ?
>
> At the moment, I copy everything that is in
> jakarta-cactus/dist/jakarta-cactus* to
> /www/jakarta.apache.org/builds/jakarta-cactus/nightly .
I guess you mean jakarta-cactus/dist/cactus-* (where * = 22 or 23) ?
However, I don't think this is true seen the result for the 21/08 for
example. For the following reasons :
- In jakarta-cactus/dist/cactus-*, there are no zip file but in
/www/jakarta.apache.org/builds/jakarta-cactus/nightly/2001-09-21 you find a
zip named jakarta-cactus-22-20010921.zip. Maybe you do a zip a everything in
jakarta-cactus/dist/cactus-* before copying ?
- In jakarta-cactus-22-20010921.zip, you'll find a target directory but none
exist in jakarta-cactus/dist/cactus-* (as no build is done in the dist
directory)
- some other reasons.
Now, what I would really like to be copied in
/www/jakarta.apache.org/builds/jakarta-cactus/nightly are the following
files that are generated by the Cactus build process (dist.gump target) :
- jakarta-cactus/dist/jakarta-cactus-22-20010921.zip
- jakarta-cactus/dist/jakarta-cactus-23-20010921.zip
- jakarta-cactus/dist/jakarta-cactus-src-20010921.zip
I do not need the jakarta-cactus/dist/cactus-* files. They are there mainly
so that other frameworks who use Cactus can find the expanded jars in
jakarta-cactus/dist/cactus-*/lib (and so that gump can reference these jars
from other project definition).
> If it isn't
> posted, it is because it isn't built. If it isn't built, you can see why
> by going to http://jakarta.apache.org/builds/gump/latest/ . In this case,
> you might have a greater likelihood of success if you were to rearrange
the
> dependencies so that dist.gump appeared before tests in the gump target.
I'll check that just after writing this email.
>
> Now onto other questions, in no particular order.
>
> I obviously do build a large number of projects on a regular basis. If
> there are any byproducts of that process that some people would find
> useful, then I will gladly upload them. Different groups have asked for
> different things, and I have tried to be accommodating. I don't insert
> value judgements into what is or is not appropriate - if I build it and
> somebody wants access to the results, then I will try to accommodate.
yes and I do really appreciate all your work Sam ! I am one of your fan !
;-)
> This
> being said (1) if I don't build it, then I can't upload it; and (2) no, I
> will not put in place a general mechanism by which anybody can copy any
> file on my machine to literally any place I have update access to on the
> Apache machines.
I've never asked for this, have I ? If I have, then dismiss it as this is
not my intent.
>
> You can see the project definitions which were used in any given build by
> clicking on the "definition" link on the corresponding build page. In
> order to have predictable jar names, I have inserted version="gump"
> properties on various projects (I have not found this to be necessary for
> Cactus to date). Alternate solutions - preferably in the form of patches
;
> -) - are always welcome.
I'm not sure I understand why you do this ? What do you think about the
issues I have raised on the subject of naming the generated jars
xxx-gump.jar ?
>
> Finally, I do believe that the actual files I posted for cactus are the
> results of the build process for cactus, and totally under the control of
> the build.xml.
> The only thing I have done is to specify where to find
> dependent jars, where to find tomcat-33, and what port to use for tests.
> Vincent - I am curious as to why you don't believe this to be the case.
> Are these not the files which the gump target would place into the dist
> directory?
For the reasons mentionned above, I don't think they are the files generated
by the dist.gump target.
>
> - Sam Ruby
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
