Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 67573 - KEEPONE property must be set at the end of a synchronize job
Summary: KEEPONE property must be set at the end of a synchronize job
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 RC3   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-16 22:56 EDT by Jean-Michel Lemieux CLA
Modified: 2004-06-18 13:26 EDT (History)
1 user (show)

See Also:


Attachments
patch (2.35 KB, text/plain)
2004-06-18 09:27 EDT, Jean-Michel Lemieux CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Michel Lemieux CLA 2004-06-16 22:56:30 EDT
3.0 RC2

I the keepone property is to work as designed, it will have to be updated at the
end of the job. We use the property to indicate is the progress viewer should
keep the job task info in the view after the job as completed. We have decided
that synchronize jobs should be kept if run in the background, and not kept if
run in the foreground. Our synchronize job is currently only setting the
property when created which is causing all synchronize jobs to be added to the view.
Comment 1 Jean-Michel Lemieux CLA 2004-06-16 22:57:01 EDT
I would like to consider for 3.0. Low risk and easy fix.
Comment 2 DJ Houghton CLA 2004-06-17 07:47:27 EDT
+1 for RC3.
Comment 3 Jean-Michel Lemieux CLA 2004-06-18 09:27:56 EDT
Created attachment 12475 [details]
patch

Easy fix, two lines-
1. use of api keepone constant that was introduced yesterday instead of
internal class
2. setting keepone at the end of the job so that if the user progress dialog
was dismissed, the job is not kept in the progress view.
Comment 4 Jean-Michel Lemieux CLA 2004-06-18 13:26:05 EDT
released.