Community
Participate
Working Groups
The problem is that it says that if another job of the same family starts, the previous job should be removed. However it looks like the test for this is incorrect. In FinishedJobs.findJobsToRemove(JobTreeElement info) it uses this test: if (job != null && job != myJob && job.belongsTo(myJob)) { The problem is that belongsTo is supposed to be passed a family. "myJob" is not a family, it is a Job. The definition of belongsTo doesn't state that you can pass a Job in. Or that it must understand a Job in addition to a family. I can see the problem though. There is no way to query what family a job is in, so there is no way to ask if two jobs are in the same family. The only way this can work is if the KEEPONE property says the belongsTo method must be able to understand a Job too, not just a family.
*** Bug 130297 has been marked as a duplicate of this bug. ***
A better implementation on our side would have been to have the KEEP_ONE properties value be the family we are looking for rather than have a boolean for enablement. That way your belongsTo would have had a much more consistant implementation. Unfortuneately this is an API change and we are past the API freeze but we should consider this for a later release. This doesn't block Bug 130297 so I will remove the dependancy
I concur with the belongsTo weirdness - it was clear from the docs that something screwy was up, and I had to check the source to figure out what it was doing with belongsTo. But on top of that, the test "job != myJob" also messes it up. If a particular instance of a Job is scheduled for a second time, and the job has the KEEPONE_PROPERTY set, the earlier run of that Job should surely be removed. But it isn't.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
