> On Friday 04 June 2004 14:22, Stefan Bodewig wrote:
> > which means it literally expects an executable command inside the
> > working directory (note the ./ at the start and the hard-coded .sh at
> > the end of the expression). You can't run arbitrary command lines
> > with <script> in "traditional" Gump.
>
> That is not what I expected, since you somehow manage to bootstrap Ant,
and
> then use Ant for all other builds, I was 'expecting' (=not really thinking
at
> all) that a similar mechanism could be used.
I think this thread is getting lost in itself. Basically if you have a
script, it can be run. If that script happens to compile some java, it can
then run it (at least via ant). That said, we could add a specialized
'builder' like we have for Ant/Maven/Script w/o woes.
As Leo would (did) say:
'There's no such thing as "friend of gump". Gump is a friend of
everyone. He's a skilled, automated, intelligent, reproducible beta (nay,
alpha) tester.'
If it isn't easy to configure/add new builders, we'll fix that...
Can you explain what you need to do (and perhaps why) and we'll see if we
need to add functionality, or not.
regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
