Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330387 - [contexts] e4 core plugins not runnable in 3.6
Summary: [contexts] e4 core plugins not runnable in 3.6
Status: RESOLVED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: E4 (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-16 13:00 EST by Erdal Karaca CLA
Modified: 2012-12-13 15:00 EST (History)
2 users (show)

See Also:


Attachments
removed 3.7 specific code parts (1.36 KB, patch)
2010-11-16 13:01 EST, Erdal Karaca CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Erdal Karaca CLA 2010-11-16 13:00:22 EST
When working in 3.6, the core plugins will not work anymore as there are quite minor dependencies on equinox 3.7 in org.eclipse.e4.core.internal.contexts.osgi.ContextDebugHelper.getDebugger()
Comment 1 Erdal Karaca CLA 2010-11-16 13:01:07 EST
Created attachment 183249 [details]
removed 3.7 specific code parts
Comment 2 John Arthorne CLA 2010-11-16 14:53:53 EST
Generally speaking, we don't attempt to support running arbitrary bundles taken from 3.7/4.1 streams in older releases such as 3.6. I.e., referencing OSGi R4.3 APIs here is quite reasonable. We could release this patch, but there is nothing stopping these references from reappearing later in the development cycle.
Comment 3 Oleg Besedin CLA 2010-11-18 09:33:39 EST
If I do this change, I'd be getting a compiler warning when run against the current OSGi bundle:

   ServiceReference is a raw type. References to generic type 
   ServiceReference<S> should be parameterized...

(In reply to comment #2)
> Generally speaking, we don't attempt to support running arbitrary bundles taken
> from 3.7/4.1 streams in older releases such as 3.6.

+1.