[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cross-project-issues-dev] Concurrent support for old and new APIs.
|
Hi
The MDT/OCL is making an API breaking change and so is taking a major increment from 1.3.0 to 3.0.0 for Helios.
[The 2.0.0 is skipped since 1.3.0 already contained a 2.0.0 plugin.]
In order to preserve API compatibility for existing customers the 1.3.0 functionality for Galileo will be preserved in 1.4.0 for Helios.
Initially we wanted to make most of the plugins in 1.4.0 and 3.0.0 have the same names but differ by bundle version only. For
instance there would be org.eclipse.ocl_1.4.0.qualifier.jar for MDT OCL 1.4.0 and org.eclipse.ocl_3.0.0.qualifier.jar for MDT OCL
3.0.0. However, for the case when 1.4.0 and 3.0.0 are installed together into the same target platform this seems not to be working.
This is so because p2 fails to install bundles that have the same name but different version.
We therefore plan to rename the org.eclipse.ocl-based names to ocl.eclipse.ocl20a to avoid the p2 problems. [20a represents the
first attempt to codify the Eclipse resolutions of OMG 2.0 specification problems.]
Questions: Is it right to rename plugins and features (but not packages or extension points)? Is p2 at fault in forcing us to
rename? Are we wrong to try to provide API compatibility in an alternate release? Is there a better solution?
If you are able to help us please comment on https://bugs.eclipse.org/bugs/show_bug.cgi?id=293605.
Regards
Ed Willink (on behalf of Alexander Igdalov)
