Bug 16912 - [ExternalTools] Running External Tool progress monitor too granular
Summary: [ExternalTools] Running External Tool progress monitor too granular
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Simon Arsenault CLA
QA Contact:
URL:
Whiteboard:
Keywords: ui
Depends on:
Blocks:
 
Reported: 2002-05-22 12:50 EDT by Adam Schlegel CLA
Modified: 2002-09-18 13:59 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Schlegel CLA 2002-05-22 12:50:04 EDT 
When running an Ant script that will take a long time to execute, a 
ProgressMonitorDialog is opened. However, the progress indicator inside the 
dialog fills up completely almost immediately, and does not accurately reflect 
how long the Ant script will take to run.
Comment 1 Adam Schlegel CLA 2002-05-22 12:56:18 EDT 
I created an external tool to run the UI tests multiple times, and also got 
unexpected behaviour from the progress indicator. The UI tests need to open 3 
Eclipse workbenches in sequence. During the first run, each workbench that got 
opened resulted in the progress indicator filling about 1/3 of the way, and 
looked full at the end of the first run. However, the external tool specified 
that the tests were to run at least 3 more times, which amounts to invoking 3 
more targets in the Ant script.

Note, the behaviour seen in this case for the first test run is not the same as 
encountered when tring to run the tests only once. When running the tests once, 
the progress indicator fills up almost immediately, not by thirds for each 
workbench opened.
Comment 2 Simon Arsenault CLA 2002-05-29 11:45:55 EDT 
Adam,

With the latest external tool support, we are using passing the monitor to 
ant.core so it should reflect better the work to be done. Can you try this out 
and let me know.
Comment 3 Simon Arsenault CLA 2002-09-06 14:45:14 EDT 
This was fixed in the 2.0 stream