[NEW] Exit-Task (was: Re: Fail task)

[Nico Seessle <ni...@seessle.de>]

If everybody can live with the name exit you can use the one I wrote some
days ago. It's named exit because in the first Version it just did
System.exit(1) in execute, now it throws a BuildException using a message if
it was given one or "no message" if not.

You can rename it to (fail|abort|break|error|<your name here>) if you think
it should have a better name :-)

I have not included a patch for
/org/apache/tools/ant/taskdefs/defaults.properties - should I do so if
submitting new Tasks?

----- Original Message -----
From: "Eric VanLydegraf" <er...@kinzan.com>
To: <an...@jakarta.apache.org>
Sent: Wednesday, September 06, 2000 9:49 PM
Subject: RE: Fail task


> <exit> :)
>
> I've got a hacky solution I currently use
> <java classname="_fail" />
>
> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@bost.de]
> Sent: Monday, September 04, 2000 11:57 PM
> To: ant-dev@jakarta.apache.org
> Subject: Re: Fail task
>
>
> >>>>> "PD" == Peter Donald <do...@mad.scientist.com> writes:
>
>  PD> Hi, would it be possible to create a task that's sole purpose was
>  PD> to fail with a message.
>
> Possible and simple (you know that 8^).
>
> I've once proposed one named <die> (must be some Perl still hiding in
> my brain). Wanna play "name that task"?
>
> Stefan

Re: [NEW] Exit-Task (was: Re: Fail task)

[Stefan Bodewig <bo...@bost.de>]

You might have noticed, I've named it <fail>, as this is closer to
what it actually does (exit doesn't imply that anything went wrong for
me).

>>>>> "NS" == Nico Seessle <ni...@seessle.de> writes:

 NS> I had other entries in my defaults.properties (for some tasks I'm
 NS> just writing but which are not finished), so I had to remove
 NS> their entries to get the "correct" patch from cvs?

I handle this more or less the same way. I work on major changes in a
separate copy - things I don't expect to finish within a day or
two.

 NS> Maybe index.html should be split up and every task given his own
 NS> file?

Split up, yes. Once we change the interface for optional tasks, each
one will need to provide it's own documentation anyway.

Stefan

Re: [NEW] Exit-Task (was: Re: Fail task)

[Nico Seessle <ni...@seessle.de>]

OK, here we go...

Just another two questions:

How do you (or others) handle this? I had other entries in my
defaults.properties (for some tasks I'm just writing but which are not
finished), so I had to remove their entries to get the "correct" patch from
cvs?

Maybe index.html should be split up and every task given his own file? I
found it very difficult to edit such a large file and don't get it wrong,
but maybe I'm using just the wrong tools :-)

Nico

----- Original Message -----
From: "Stefan Bodewig" <bo...@bost.de>
To: <an...@jakarta.apache.org>
Sent: Thursday, September 07, 2000 9:06 AM
Subject: Re: [NEW] Exit-Task (was: Re: Fail task)


> >>>>> "NS" == Nico Seessle <ni...@seessle.de> writes:
>
>  NS> I have not included a patch for
>  NS> /org/apache/tools/ant/taskdefs/defaults.properties - should I do
>  NS> so if submitting new Tasks?
>
> Yes please, as well as a patch to docs/index.html (and additional docs
> if necessary) - at least that is what I'd prefer to get patches
> commited as fast as possible.
>
> Stefan

Re: [NEW] Exit-Task (was: Re: Fail task)

[Stefan Bodewig <bo...@bost.de>]

>>>>> "NS" == Nico Seessle <ni...@seessle.de> writes:

 NS> I have not included a patch for
 NS> /org/apache/tools/ant/taskdefs/defaults.properties - should I do
 NS> so if submitting new Tasks?

Yes please, as well as a patch to docs/index.html (and additional docs
if necessary) - at least that is what I'd prefer to get patches
commited as fast as possible.

Stefan