Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 80795 invoked from network); 10 Nov 2000 03:55:05 -0000 Received: from unknown (HELO smtp.cortexebusiness.com.au) (203.174.140.214) by locus.apache.org with SMTP; 10 Nov 2000 03:55:05 -0000 Received: (from daemon@localhost) by smtp.cortexebusiness.com.au (8.10.0/8.10.0) id eAA3t3F13471; Fri, 10 Nov 2000 14:55:03 +1100 (EST) Received: from UNKNOWN(192.168.1.8), claiming to be "monkey.prod.thespot.com.au" via SMTP by ripley, id smtpdAAApHaWgA; Fri Nov 10 14:54:59 2000 Received: (from daemon@localhost) by monkey.prod.thespot.com.au (8.10.0/8.10.0) id eAA3swS22386; Fri, 10 Nov 2000 14:54:59 +1100 (EST) Received: from UNKNOWN(192.168.1.9), claiming to be "chunky.devl.ebinteractive.com.au" via SMTP by monkey, id smtpdAAAOgayTR; Fri Nov 10 14:54:57 2000 Received: from snotty (snotty.devl.ebinteractive.com.au [192.168.1.32]) by chunky.devl.ebinteractive.com.au (8.10.0/8.10.0) with SMTP id eAA3suB16438; Fri, 10 Nov 2000 14:54:56 +1100 (EST) From: "Conor MacNeill" To: , Subject: RE: [PATCH] UnknownElement Date: Fri, 10 Nov 2000 14:55:09 +1100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-reply-to: X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Erik, Thanks for re-sending that. I did apply this change locally but I haven't committed yet for two reasons: 1. The message is now getting pretty long and I thought perhaps it should be formatted rather than one huge line 2. I am not sure of the target audience of this message. If we are targeting users who download a binary distribution, then telling them to bootstrap/build is not that cool since those scripts are not even included in the binary distribution. It is not a big deal, but I thought we should just think about who we expect to get this message and under what circumstances. What do you think? -- Conor MacNeill conor@cortexebusiness.com.au Cortex eBusiness http://www.cortexebusiness.com.au > -----Original Message----- > From: Erik Meade [mailto:emeade@geekfarm.org] > Sent: Friday, 10 November 2000 14:22 > To: ant-dev@jakarta.apache.org > Subject: RE: [PATCH] UnknownElement > > > I'm reposting this as it didn't get commited, folks still ask > about it. > > > -----Original Message----- > > From: Erik Meade [mailto:emeade@geekfarm.org] > > Sent: Wednesday, October 25, 2000 6:12 PM > > To: ant-dev@jakarta.apache.org > > Subject: RE: [PATCH] UnknownElement > > > > > > Now reads: if this is an optional task put the optional.jar in the > > lib directory of your ant installation (ANT_HOME) > > > > > -----Original Message----- > > > From: Conor MacNeill [mailto:conor@m64.com] > > > Sent: Wednesday, October 25, 2000 5:42 AM > > > To: ant-dev@jakarta.apache.org; emeade@geekfarm.org > > > Subject: RE: [PATCH] UnknownElement > > > > > > > > > Erik, > > > > > > Perhaps it would be better to say "put optional.jar in the > lib directory > > > of your ant installation (ANT_HOME)" > > > What do you think? > > > > > > Conor > > > > > > > -----Original Message----- > > > > From: Erik Meade [mailto:emeade@geekfarm.org] > > > > Sent: Wednesday, 25 October 2000 15:13 > > > > To: ant-dev@jakarta.apache.org > > > > Subject: RE: [PATCH] UnknownElement > > > > > > > > > > > > Added in putting option.jar in your classpath if it is an > > > > optional task. > > > > > > > > > -----Original Message----- > > > > > From: Erik Meade [mailto:emeade@geekfarm.org] > > > > > Sent: Thursday, October 12, 2000 7:31 PM > > > > > To: ant-dev@jakarta.apache.org > > > > > Subject: RE: [PATCH] UnknownElement > > > > > > > > > > > > > > > Added in Nico's suggestion. > > > > > Erik > > > > > > > > > > > -----Original Message----- > > > > > > From: Erik Meade > > > > > > Sent: Thursday, October 12, 2000 7:10 AM > > > > > > To: ant-dev@jakarta.apache.org > > > > > > Subject: RE: [PATCH] UnknownElement > > > > > > > > > > > > > > > > > > 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 > > > > > > > Sent: Thursday, October 12, 2000 12:35 AM > > > > > > > To: ant-dev@jakarta.apache.org > > > > > > > Subject: Re: [PATCH] UnknownElement > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Erik Meade" > > > > > > > To: > > > > > > > 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 > > > > > > > >