ok. Jan
> -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 07, 2004 6:15 PM > To: [EMAIL PROTECTED] > Subject: Re: little error in <presetdef> > > > On Wed, 7 Apr 2004, Jan Materne <[EMAIL PROTECTED]> wrote: > > > I think it would be better to show the original taskname (in > > contrast to the other *def tasks) because presetdef only takes one > > task/type and finding the error would be easier. > > It depends. In your case havig the error message talk about the > original task would be a better solution. > > But consider a scenario where I import a snippet written by my > buildmeister. He has told me that this snippet will make a task named > <x> available to me - no more details. I don't need to know whether > it is a macro, a script, a task loaded as antlib or plain task, I just > want to use it. > > If then the error message talks about echo when I've been using x in > the line the message is talking about, I'd probably be even more > confused. > > Stefan > -- > http://stefanbodewig.blogger.de/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
