Probably, at the risk of appearing uninformed... what is involved with using taskdef to declare you task? I've created new tasks, so my guess is I've done this, but I'm not sure I know what I did... I'll send another patch tonight or tomorrow and add it in above "add the task to the defaults.properties" as suggested by Stefan.
Erik Meade > -----Original Message----- > From: Nico Seessle [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 12, 2000 12:35 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: [PATCH] UnknownElement > > > ----- Original Message ----- > From: "Erik Meade" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, October 12, 2000 6:59 AM > Subject: [PATCH] UnknownElement > > > > I thought it may be a good idea to list some solutions with > > the maybeConfigure build exception. > > > > Erik Meade > > "1 execute bin/bootstrap. > 2 add the task to the defaults.properties." > > Isn't this missing "3 use taskdef to declare your task?" > > Nico >
