Bug 272735 - [jobs] JobManager hides constants for status code
Summary: [jobs] JobManager hides constants for status code
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: api
Depends on:
Blocks:
 
Reported: 2009-04-17 14:00 EDT by Kevin McGuire CLA
Modified: 2022-01-29 16:39 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin McGuire CLA 2009-04-17 14:00:03 EDT
JobManager declares constants which are used for the status codes.
The purpose of a status code is that someone inspecting the status could know the nature of the error.  Thus these keys should be publically accessible so comparisons can be made.

e.g.
	public static final int PLUGIN_ERROR = 2;

(not sure if there are others)
Comment 1 Kevin McGuire CLA 2009-04-17 14:00:28 EDT
Note JobManager is in an internal package.
Comment 2 John Arthorne CLA 2009-04-17 14:35:59 EDT
This constant is copied because we can't reference the API Platform.PLUGIN_ERROR. However we should redefine API for this constant so clients also don't need to rely on API in the Platform class.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:10:53 EDT
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.
Comment 4 Eclipse Genie CLA 2022-01-29 16:39:40 EST
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.