| Summary: | [contexts] e4 core plugins not runnable in 3.6 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Erdal Karaca <erdal.karaca.de> | ||||
| Component: | E4 | Assignee: | Project Inbox <e4.runtime-inbox> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | john.arthorne, ob1.eclipse | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Erdal Karaca
Created attachment 183249 [details]
removed 3.7 specific code parts
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. 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. |