| Summary: | org.eclipse.core.jobs does not export packages with version | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Gunnar Wagenknecht <gunnar> |
| Component: | Runtime | Assignee: | platform-runtime-inbox <platform-runtime-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | john.arthorne, remy.suen |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Gunnar Wagenknecht
Thoughts on this John? Sounds reasonable to me. I'm dying to hear about all the alternate implementations of the org.eclipse.core.jobs package out there ;) 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. |