Noel wrote,
> > But the point of Gump is that it tests the domain level build
> by building
> > every part of the domain from scratch.
>
> That assumes that the domain is evolving in synch, and is intended to be
> released in synch. It works great for a domain level project, but that's
> not necessarily the case.
No, but it is the premis of Gump, as I understand it, that it encourages
continuous integration within the jakarta domain.
<snipped dull comment from self/>
> From that perspective, I could see two nightly builds: a domain
> level build,
> and the other a build of James against the components that it is
> intended to
> work with.
Its certainly reasonable to suggest a self-contained nightly build of James,
the problem is resources, the apache machines ('cept nagoya) run BSD so we
can't build on them, therefore someone needs to donate the build location.
I changed build.xml to put the downloads into a directory that can be scp'ed
across by a single command to make automatic releases easier, and I have a
"clean" machine that I build releases on, but I wouldn't like James to rely
on it, as its continued presence is outwith my control.
I would also be wary of entrusting my apache password or keys to a machine
on which there are other people with root.
Hence the reason I instigated the "latest" directory, to make builds
available at random when it seems worthwhile, and that aren't deleted by
someones cron job.
Anyone is welcome to cajole us into putting a new version in latest.
d.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
