I might be suffering from too much turkey and seasonal brain-fog, but when I started using ant, I began with little tiny scripts where the effects (or not) were immediately obvious and if something looked funny, or I didn't understand it, then I ran ant with the "-v" option to get more details on what ant thought it was doing versus what I thought it should be doing. I have not found a need to ever use <echo> to date.
Remember, very large build scripts are made by adding one target, or task, at a time to very small build scripts! :-) Hope this helps, Simon ----------------------------------------------------------------- Simon P. Chappell [EMAIL PROTECTED] Java Programming Specialist www.landsend.com Lands' End, Inc. (608) 935-4526 >-----Original Message----- >From: John Volkar [mailto:[EMAIL PROTECTED]] >Sent: Thursday, December 27, 2001 8:46 AM >To: [EMAIL PROTECTED] >Subject: Newbie help <echo> > > >Okay, I'm new, so bear with me. > >I'm trying to setup the beginnings of a fairly large build >script, that we >will use in a nightly/weekly build process. Eventually, >automatic email >notifications, and all the trimming will be added, but.... >First I need to >walk before I can run, so... I'm simply using the <echo> task >to give some >feedback as I develop my scripts. > >Is echo output caught by the email notifiers automatically >when those are >added? I mean would I be wasting my time createing nice clear >meaningful >messages for the <echo>'s? If the email notifiers catch the <echo>'d >output, then it's time well spent. > >Thanks > >John Volkar > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
