[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] Runtime split changes
|
A clarification on the impact of the runtime refactoring on self-hosting:
Using today's I-build, all existing launch configurations (Eclipse
application and Plug-in JUnit) will continue to work as if nothing
happened
The first time you launch or open an existing launch configuration of said
types, the launch configuration will undergo a one-time migration step
under the cover to adjust its startup sequence to reflect the new
refactored world.
Backward Compatibility: Supported - as always
As long as your target platform is <= your host, things will continue to go
swimmingly.
Forward Compatibility: NOT supported - as always
You will not be able to use for example 3.2M3 (or earlier) as your host,
I-20051122 (or later) as your target, and expect runtime Eclipse
applications to start. They won't.
Thank you.
The PDE team.
Jeff
McAffer/Ottawa/IB
M@IBMCA To
Sent by: eclipse-dev@xxxxxxxxxxx,
eclipse-dev-bounc platform-releng-dev@xxxxxxxxxxx
es@xxxxxxxxxxx cc
Subject
11/21/2005 08:14 [eclipse-dev] Runtime split changes
PM
Please respond to
"General
development
mailing list of
the Eclipse
project."
You have probably noticed a few new Equinox plugins appearing in the last
few nightly builds. These are by-products of the runtime refactoring effort
(see https://bugs.eclipse.org/bugs/show_bug.cgi?id=113663). The changes
have been committed to the main repo and are in today's integration build.
We have done several test builds (thanks Sonia and Kim!) to work out the
kinks. There have been a few test failures but all known issues have been
resolved or reported to the relevant teams.
We have documented the changes and some of the issues in a migration guide
at
http://eclipse.org/equinox/documents/3.2-migration.php
PDE has been updated to accomodate the new structure (thanks Wassim).
Despite their heroic efforts, there is a chance that some launch
configurations, hardcoded scripts and plugin-list based product
configurations will need to be updated to reflect the new plugin structure.
Please take a look at the new API and structure and let the Equinox team
(on equinox-dev or in bug reports) know if you have any questions/issues.
Note that some of the new API is in flux and is likely to change over the
course of M4. We will continue to update the migration guide as these
changes become more concrete and we can provide guidance on how to adopt
the new API.
The Equinox Team_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
