What I did for the progress bar in Antelope is to count the number of
tasks to be executed, then created a build listener that increased the
bar on each task completion. The tricky part is counting the number of
tasks in advance. While this doesn't give a time estimate, it does give
a pretty good indication of how far along the build is, percentage-wise.
Dale
Rebhan, Gilbert wrote:
-----Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 07, 2007 1:21 PM
To: Ant Users List
Subject: Re: target progress bar
/*
At its most rigorous, predicting how long something will take to
complete requires a solution to the halting problem: a way to predict
when/whether something will terminate.
However, remembering how long something took last time is a good metric,
and is generally what things like grid workload schedulers do. If you
submit a job "to the grid", it remembers how long this took last time
and uses that as a metric of what is likely to be needed.
For ant you could have some profile listener that knows how long
specific targets/tasks took, and the next run, moves the progress
forwards.
*/
OK, that might be possible, f.e. with a tool like
https://antutility.dev.java.net/
a BuildMetricListener.
Regards, Gilbert
---------------------------------------------------------------------
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]
