Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 68150 - [Progress] ProgressViewUpdater sends no updates for first job
Summary: [Progress] ProgressViewUpdater sends no updates for first job
Status: RESOLVED DUPLICATE of bug 82146
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 63539 67997 68451 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-06-22 06:31 EDT by Andre Weinand CLA
Modified: 2005-01-05 10:53 EST (History)
4 users (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 Andre Weinand CLA 2004-06-22 06:31:38 EDT 
RC3

- open JobFactory and ProgressView
- press "Create Jobs" button
Observe: no job is shown

- press "Create Jobs" button again
Observe: ProgressViewer shows two jobs

It seems that the ProgressViewUpdater does not send out notification for the first job.
Comment 1 Andre Weinand CLA 2004-06-22 07:23:08 EDT 
*** Bug 63539 has been marked as a duplicate of this bug. ***
Comment 2 Andre Weinand CLA 2004-06-22 08:47:45 EDT 
*** Bug 67997 has been marked as a duplicate of this bug. ***
Comment 3 Tod Creasey CLA 2004-06-22 09:56:37 EDT 
I can't make this happen consistently (although I have seen it in the past). 
I'll leave this open but I don't think we want to do anything for 3.0.
Comment 4 Tod Creasey CLA 2004-06-22 10:54:04 EDT 
This is likelu related to Bug 68151
Comment 5 Andre Weinand CLA 2004-06-22 19:09:28 EDT 
I see this behavior always.
Comment 6 Andre Weinand CLA 2004-06-24 03:58:56 EDT 
*** Bug 68451 has been marked as a duplicate of this bug. ***
Comment 7 John Arthorne CLA 2005-01-05 10:53:51 EST 
I'm fairly certain this is a duplicate of a core bug that I fixed yesterday.  If
anyone sees this after the next integration build (I20050111), please reopen.

*** This bug has been marked as a duplicate of 82146 ***