2005 6:43 AM
> > To: Ant Users List
> > Subject: using tstamp to time a macro execution
> >
> >
> > I currently have a macro definition like so:
> >
> >
> >
> >
> >
> > classname="com.compiler.compiler"
> > c
p
> properties.
> and one with a prefix of end.
> Then you can use ${start.BUILD_TIMESTAMP} and ${end.BUILD_TIMESTAMP}
>
> > -Original Message-
> > From: Mark Lybarger [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, July 14, 2005 7:24 AM
> > To: Ant Users L
> To: Ant Users List
> Subject: Re: using tstamp to time a macro execution
>
>
> thanks for the suggestion, but i'm not sure i can introduce
> ant-contrib
> tasks.
>
> On 7/14/05, Shatzer, Larry <[EMAIL PROTECTED]> wrote:
> >
> > Ant-contrib h
look at their performance monitor:
> http://ant-contrib.sourceforge.net/tasks/tasks/performance_monitor.html
>
> > -Original Message-
> > From: Mark Lybarger [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, July 14, 2005 6:43 AM
> > To: Ant Users List
> >
[EMAIL PROTECTED]
> Sent: Thursday, July 14, 2005 6:43 AM
> To: Ant Users List
> Subject: using tstamp to time a macro execution
>
>
> I currently have a macro definition like so:
>
>
>
>
>
> classpathref="compiler.run.cl
I currently have a macro definition like so:
http://compiler.run.classpath.id>">
Completed Compile of @{projectDir} At: ${BUILD_TIMESTAMP}
the issue is that when i call it twice, i get the same time stamp output.
this is b/c properties are immutable. it'd be nice to be able to time
