Just to interject myself in the conversation :-) The main usage for me of recording is to be able to extract the output of specific (probably scatered) sections of the build (maybe with a higher level of logging).
For that, you really need the to be able to stop and start the recorder as many times as you may want (which means appending). Going back to the bug text, I see that the original problem most probably had to do with Netbeans keeping the static environment of ANT around and therefore ANT does not know whether this is the first time <record/> is called on the build or not. This is a very specific situation, applicable to those environments that cache ANT classes (how does this interacts with the new loader stuff I do not know). In any case, maybe what we need is a way to tell <record/> to reset itself <record action="reset"/> which will make the task to act as if on a newly created JVM. So Netbeans and other IDE users could add such statement to their top-level buildfile or having it as a separate call done before calling the main project. Opinions? Jose Alberto > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: 12 January 2004 11:34 > To: [EMAIL PROTECTED] > Subject: Re: DO NOT REPLY [Bug 26020] New: - Writing to a file. > > > On Mon, 12 Jan 2004, Conor MacNeill <[EMAIL PROTECTED]> > wrote: > > > The scenario we have to cater for is a single recorder class (and > > associated static table) spanning multiple builds. > > What does the current implementation do in this case? > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
