Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 772 invoked from network); 4 Apr 2002 16:03:33 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 4 Apr 2002 16:03:33 -0000 Received: (qmail 14265 invoked by uid 97); 4 Apr 2002 11:43:57 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 14250 invoked by uid 97); 4 Apr 2002 11:43:57 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 14237 invoked from network); 4 Apr 2002 11:43:57 -0000 Message-Id: <200204041142.g34Bgpi10223@mail021.syd.optusnet.com.au> Content-Type: text/plain; charset="utf-8" From: Peter Donald To: "Ant Developers List" Subject: Re: possible bug in ChangeLog task Date: Thu, 4 Apr 2002 21:38:47 +1000 X-Mailer: KMail [version 1.3.2] References: <3CAB1582.3010309@castify.net> In-Reply-To: <3CAB1582.3010309@castify.net> X-Wisdom-Cookie: . MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, 4 Apr 2002 00:45, Frederic Lavigne wrote: > I've tested the changelog and found a possible bug in the log parser. > processGetPreviousRevision method sets the status to GET_COMMENT but it > should set it to GET_DATE otherwise the date information gets put in the > comment damn - fixed. I also fixed it so that the time is actually recorded now aswell - previously it was just reading the date and ignoring the time field ;) > and as the author is escaped using a CDATA, you finally get a CDATA > inside a CDATA... I reworked this so that no matter what this should never happen by placing the CDATA escaping in the writer. > Am I right ? completely! patch applied ;) > Also I've encountered some problems when cvs log is executed. The process > hangs forever and the changelog command never ends. I modified the > Changelog command to send the cvs log output to a temporary file (I reuse > the cvs task for that) and then I pass this file to the parser. Can't reproduce but I suspect that it has something to do with the error stream not being read from until the end of parsing. Now the stderror is processed in a separate thread and this *should* fix it - if that was the problem. Could you download again and see if it works for you ! -- Cheers, Pete ------------------------------------------------------- "When we remember we are all mad, the mysteries of life disappear and life stands explained." -Mark Twain ------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: