The manual contains information about contributing in the section "Developing with Ant | Ant Task Guidelines" (http://ant.apache.org/ant_task_guidelines.html)
The tutorial "Tasks using Properties & Filesets" uses that for explaining how to contribute a new task. (document not finished yet) But maybe the informations already present will help you. http://cvs.apache.org/viewcvs.cgi/*checkout*/ant/docs/manual/tutorial-tasks- filesets-properties.html?rev=1.2&content-type=text/plain#contribute Directly to the first question in the "Contribute" area of the tutorial "is our task welcome? :-) Simply ask on the user list" I thought for myself to implement a TeeLogger, so please contribute it :-) Jan > -----Original Message----- > From: Ron Coutts [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 03, 2003 7:46 AM > To: [EMAIL PROTECTED] > Subject: TeeLogger class > > > One problem that I've had with Ant is that the logging > facilities allow > directing the output to either the console or a log file, but > typically > not both. This is fairly restrictive when you want to watch the > progress of a build and have an log of build that is identical to what > went by on the console. So in the spirit of the 'tee' command line > utility I've developed a TeeLogger class that extends > DefaultLogger and > works a bit like MailLogger and a bit like XmlLogger. It can > direct log > output to two sinks simultaneously such as to the console and > a file or > to two files at the same time (not that this latter feature is worth > much). > > Here are some examples of specifying TeeLogger on the Ant > command line: > > ant -logger com.envistatech.tools.ant.TeeLogger > Directs log output to console and log.txt by default. > > ant -logger com.envistatech.tools.ant.TeeLogger > -DTeeLogger.file=mylog.txt > Directs log output to console and mylog.txt. > > ant -logger com.envistatech.tools.ant.TeeLogger > -DTeeLogger.file=mylog.txt -logfile mylog2.txt > Directs log output to mylog.txt and mylog2.txt. > > > I think this might be useful to others and I wouldn't mind > contributing > it. So my questions are, is this a worthy contribution and > if so what's > happens next? This would be my first code contribution and I'm not at > all familiar with the process of contributing code. > > Ron > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
