Ant-contrib has a stopwatch task: http://ant-contrib.sourceforge.net/tasks/tasks/stopwatch_task.html
You also might want to 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 > Subject: using tstamp to time a macro execution > > > I currently have a macro definition like so: > > <macrodef name="compile.sub.project"> > <attribute name="projectDir" default="ERROR"/> > <sequential> > <!-- TODO: failure here should fail the build. --> > <java fork="true" dir="${basedir}" classname="com.compiler.compiler" > classpathref="compiler.run.classpath.id > <http://compiler.run.classpath.id>"> > <arg value="../@{projectDir}/build"/> > </java> > <tstamp> > <format property="BUILD_TIMESTAMP" pattern="MMM dd yyyy HH:mm:ss"/> > </tstamp> > <echo>Completed Compile of @{projectDir} At: ${BUILD_TIMESTAMP}</echo> > </sequential> > </macrodef> > > 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 the > execution of the macrodef, display start/stop time, and even time > difference. ideas? suggestions? > > thanks! > ~mark > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
