Summary: | [Progress] IProgressConstants.KEEPONE_PROPERTY is forced to use poor implementation of belongsTo | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Richard Kulp <richkulp> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | john.arthorne, markus.kell.r |
Version: | 3.1.1 | Keywords: | api, greatbug |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Richard Kulp
2005-10-17 18:14:10 EDT
*** 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. 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. |