Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338304 - org.eclipse.core.jobs does not export packages with version
Summary: org.eclipse.core.jobs does not export packages with version
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-26 07:08 EST by Gunnar Wagenknecht CLA
Modified: 2011-07-07 10:49 EDT (History)
2 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 Gunnar Wagenknecht CLA 2011-02-26 07:08:29 EST 
It would be nice if org.eclipse.core.jobs could export the public API packages with a version. This would allow downstream consumers to move from require bundle to import package.
Comment 1 DJ Houghton CLA 2011-02-28 13:20:19 EST 
Thoughts on this John? Sounds reasonable to me.
Comment 2 John Arthorne CLA 2011-02-28 13:30:34 EST 
I'm dying to hear about all the alternate implementations of the org.eclipse.core.jobs package out there ;)
Comment 3 John Arthorne CLA 2011-07-07 10:49:26 EDT 
The jobs bundle consists of one API package and one implementation package. These two packages must go together - for example the API class Job has a superclass in the implementation package. So, using Import-Package here would be a false flexibility - it was never designed to be consumed at package granularity. Adding version to the package would just add one extra step for me when making changes (which I will probably forget to make), and offers no benefits in return.