Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 89001 invoked by uid 500); 9 May 2001 09:43:53 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 88919 invoked from network); 9 May 2001 09:43:43 -0000 Message-Id: <3.0.6.32.20010509194814.00afb100@mail.alphalink.com.au> X-Sender: gdonald@mail.alphalink.com.au X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 09 May 2001 19:48:14 +1000 To: ant-dev@jakarta.apache.org From: Peter Donald Subject: Re: [Vote] Logging In-Reply-To: References: <3.0.6.32.20010508232432.00a71e00@mail.alphalink.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N At 11:33 9/5/01 +0200, Stefan Bodewig wrote: >Peter Donald wrote: > >> I would like to do Ant2 logging with logkit. > >I'm completely with Conor here - logging should be done through >BuildListeners - feel free to write one for Logkit or Log4J or >whatever. I don't know where it got confused but thats not the use of the logging toolkit. The logging toolkit is meant to act as a log "router" between tasks and listeners. I have said at least 4 times that the output Appenders/LogTargets would unlikely to be used ... >I don't get the point of hierarchical logging, sorry. TaskContainers >won't make that any more difficult than subbuilds already do in Ant1 - >and it is up to the BuildListener to do something with the >information, that a task is running in a subbuild (the XmlLogger uses >this info, while the DefaulLogger completly ignores it). Well try coding it - I am sure you will see my point then ;) Just in case it is not obvious the use of hierarchial logging is completely and utterly transparent to ProjectListener - they still see the same events they see now. It is the magic that occurs before that ... as someone said the best way to do it is code or at least run through the code in your head. Then hopefully you will see the difficulties. Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*