Google Git
Sign in
eclipse / www.eclipse.org / org / fabcb49dda6f64f427ff1bdbcfe35f7529e30a89 / . / councils / roadmap_v6_0 / plans / rt.equinox_plan.html
blob: b20e3b0aff54e1def25502c8b89789ebddc9f43e [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Project Plan - rt.equinox</title><meta name="author" content="Bjorn Freeman-Benson" />
<meta name="keywords" content="" />
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<link rel="stylesheet" type="text/css" href="/eclipse.org-common/yui/2.6.0/build/reset-fonts-grids/reset-fonts-grids.css" media="screen" />
<link rel="stylesheet" type="text/css" href="/eclipse.org-common/yui/2.6.0/build/menu/assets/skins/sam/menu.css" media="screen" />
<link rel="stylesheet" type="text/css" href="/eclipse.org-common/themes/Nova/css/reset.css" media="screen"/>
<link rel="stylesheet" type="text/css" href="/eclipse.org-common/themes/Nova/css/layout.css" media="screen" />
<link rel="stylesheet" type="text/css" href="/eclipse.org-common/themes/Nova/css/header.css" media="screen" />
<link rel="stylesheet" type="text/css" href="/eclipse.org-common/themes/Nova/css/footer.css" media="screen" />
<link rel="stylesheet" type="text/css" href="/eclipse.org-common/themes/Nova/css/visual.css" media="screen" />
<link rel="stylesheet" type="text/css" href="/eclipse.org-common/themes/Nova/css/print.css" media="print" />
<!--[if lte IE 7]> <link rel="stylesheet" type="text/css" href="/eclipse.org-common/themes/Nova/css/ie_style.css" media="screen"/> <![endif]-->
<!--[if IE 6]> <link rel="stylesheet" type="text/css" href="/eclipse.org-common/themes/Nova/css/ie6_style.css" media="screen"/> <![endif]-->
<!-- Dependencies -->
<!-- Source File -->
</head>
<body>
<div id="novaWrapper"> <div id="clearHeader">
<div id="logo">
<img src="/eclipse.org-common/themes/Nova/images/eclipse.png" alt="Eclipse.org"/>
</div>
<div id="otherSites">
<div id="sites">
<ul id="sitesUL">
<li><a href='http://marketplace.eclipse.org'><img alt="Eclipse Marketplace" src="http://dev.eclipse.org/custom_icons/marketplace.png"/>&nbsp;<span>Eclipse Marketplace</span></a></li>
<li><a href='http://www.youtube.com/user/EclipseFdn' target="_blank"><img alt="Eclipse YouTube Channel" src="http://dev.eclipse.org/custom_icons/audio-input-microphone-bw.png"/>&nbsp;<span>Eclipse YouTube Channel</span></a></li>
<li><a href='https://bugs.eclipse.org/bugs/'><img alt="Bugzilla" src="http://dev.eclipse.org/custom_icons/system-search-bw.png"/>&nbsp;<span>Bugzilla</span></a></li>
<li><a href='http://www.eclipse.org/forums/'><img alt="Forums" src="http://dev.eclipse.org/large_icons/apps/internet-group-chat.png"/>&nbsp;<span>Eclipse Forums</span></a></li>
<li><a href='http://www.planeteclipse.org/'><img alt="Planet Eclipse" src="http://dev.eclipse.org/large_icons/devices/audio-card.png"/>&nbsp;<span>Planet Eclipse</span></a></li>
<li><a href='http://wiki.eclipse.org/'><img alt="Eclipse Wiki" src="http://dev.eclipse.org/custom_icons/accessories-text-editor-bw.png"/>&nbsp;<span>Eclipse Wiki</span></a></li>
<li><a href='http://portal.eclipse.org'><img alt="MyFoundation Portal" src="http://dev.eclipse.org/custom_icons/preferences-system-network-proxy-bw.png"/><span>My Foundation Portal</span></a></li>
</ul>
</div>
</div>
</div>
<div id="header">
<div id="menu">
<ul>
<li><a href="/" target="_self">Home</a></li>
<li><a href="/downloads/" target="_self">Downloads</a></li>
<li><a href="/users/" target="_self">Users</a></li>
<li><a href="/membership/" target="_self">Members</a></li>
<li><a href="/committers/" target="_self">Committers</a></li>
<li><a href="/resources/" target="_self">Resources</a></li>
<li><a href="/projects/" target="_self">Projects</a></li>
<li><a href="/org/" target="_self">About Us</a></li>
</ul>
</div>
<div id="search">
<form action="http://www.google.com/cse" id="searchbox_017941334893793413703:sqfrdtd112s">
<input type="hidden" name="cx" value="017941334893793413703:sqfrdtd112s" />
<input id="searchBox" type="text" name="q" size="25" />
<input id="searchButton" type="submit" name="sa" value="Search" />
</form>
<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=searchbox_017941334893793413703%3Asqfrdtd112s&lang=en"></script>
</div>
</div>
<div id="novaContent" class="faux"> <br style="clear:both;height:1em;"/>
<div id="leftcol">
<ul id="leftnav">
<li class="separator"><a class="separator" href="/projects/">
Projects<img src="/eclipse.org-common/themes/Nova/images/separator.png"/></a></li>
<li><a href="/projects/whatsnew.php" target="_self">What's New?</a></li>
<li><a href="/projects/listofprojects.php" target="_self">List of Projects</a></li>
<li><a href="/projects/searchpage.php" target="_self">Search through Projects...</a></li>
<li><a href="/projects/dev_process/index-quick.php" target="_self">Rules &amp; Processes</a></li>
<li><a href="/projects/dev_process/index.php" target="_self">FAQ</a></li>
<li><a href="/projects/tools" target="_self">Tools for committers</a></li>
</ul>
</div>
<style>
h2 {
border-bottom: 2px solid gray;
}
h3 {
border-bottom: 1px dotted gray;
}
</style>
<div id="fullcolumn">
<div id="midcolumn">
<div xmlns="http://www.w3.org/1999/xhtml" id="rendered-plan">
<div id="maincontent">
<div id="midcolumn"><h1>
Project Plan For
<a href="http://www.eclipse.org/projects/project_summary.php?projectid=rt.equinox">Equinox</a>, version Indigo</h1><div id="toc"><p><a name="toc"><strong>Table of Contents</strong></a></p><ul><li><a href="#introduction">Introduction</a></li><li><a href="#release_deliverables">
Release Deliverables
</a></li><li><a href="#release_milestones">
Release Milestones
</a></li><li><a href="#target_environments">
Target Environments
</a></li><li><a href="#compatibility">
Compatibility with Previous Releases
</a></li><li><a href="#themes_and_priorities">
Themes and Priorities
</a></li><li><a href="#appendix">
Appendix
</a></li></ul></div><h2><a name="introduction">Introduction</a></h2><div>
<p>
Last revised 16:00 ET November 1, 2010. (<img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/>
marks interesting changes since the previous draft)
</p>
<p><i>Please send comments about this plan to the</i> <a href="mailto:equinox-dev@eclipse.org">equinox-dev@eclipse.org</a> <i>developer
mailing list.</i>
</p>
<p>The goal of the Equinox project is to be a first class OSGi community and foster the vision of Eclipse
Runtime technologies. As part of this, it is responsible for developing and delivering the OSGi
framework implementation used for all of Eclipse. Equinox is also responsible for developing
other core runtime technologies such as p2, extension registry, security and core server-side
runtime components.
</p>
<p>This document lays out the feature and API set for the next feature release
of Equinox after 3.6, designated release 3.7 and code-named Indigo.
</p>
<p>Plans do not materialize out of nowhere, nor are they entirely static. To
ensure the planning process is transparent and open to the entire Eclipse community,
we (the Equinox component leads) post plans in an embryonic form and revise them
throughout the release cycle. </p>
<p>The first part of the plan deals with the important matters of release deliverables,
release milestones, target operating environments, and release-to-release compatibility.
These are all things that need to be clear for any release, even if no features
were to change. </p>
<p>The remainder of the plan consists of plan items for all of the sub-projects
under the Equinox Project. Each plan item covers a feature or API
that is to be added to the Equinox Project deliverables, or some aspect of
the Equinox Project that is to be improved. Each plan item has its own entry
in the Eclipse bugzilla database, with a title and a concise summary (usually
a single paragraph) that explains the work item at a suitably high enough level
so that everyone can readily understand what the work item is without having
to understand the nitty-gritty detail. </p>
<p>Not all plan items represent the same amount of work; some may be quite large,
others, quite small. Some plan items may involve work that is localized to
a single component; others may involve coordinated changes to several components;
other may pervade the entire SDK. Although some plan items are for work that
is more pressing than others, the plan items appear in no particular order. </p>
<p>With the previous release as the starting point, this is the plan for how
we will enhance and improve it. Fixing bugs, improving test coverage, documentation,
examples, performance tuning, usability, etc. are considered routine ongoing
maintenance activities and are not included in this plan unless they would
also involve a significant change to the API or feature set, or involve a significant
amount of work. The intent of the plan is to account for all interesting feature
work. </p>
<p>The current status of each plan item is noted: </p>
<ul>
<li><b>Committed</b> plan item - A committed plan item is one that we have
decided to address for the release.</li>
<li><b>Proposed</b> plan item - A proposed plan item is one that we are considering
addressing for the release. Although we are actively investigating it, we
are not yet in a position to commit to it, or to say that we won't be able
to address it. After due consideration, a proposal will either be committed
or deferred.</li>
<li><b>Deferred</b> plan item - A reasonable proposal that will not make it
in to this release for some reason is marked as deferred with a brief note
as to why it was deferred. Deferred plan items may resurface as committed
plan items at a later point.</li>
</ul>
</div><h2><a name="release_deliverables">Release Deliverables</a></h2><div>
<p>The release deliverables have the same form as previous releases, namely: </p>
<ul>
<li>Source code release for all Equinox Project deliverables, available as
versions tagged "R3_7" in the Equinox Project <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.equinox/?root=RT_Project">CVS
repository</a>.</li>
<li><b>Framework:</b>
<ul>
<li>An OSGi R4.3 Core Framework implementation</li>
<li>Native launcher and splash screen support</li>
</ul>
</li>
<li><b>Compendium Services:</b>
<ul>
<li>Application Container - An implementation of the OSGi R4.3 Application Container service.</li>
<li>Config Admin - An implementation of the OSGi R4.3 Configuration Admin service.</li>
<li>Device Access Service - An implementation of the OSGi R4.3 Device Access service.</li>
<li>Declarative Services - An implementation of the OSGi R4.3 Declarative Services specification.</li>
<li>Event Admin Service - An implementation of the OSGi R4.3 Event Admin Service.</li>
<li>HTTP Service - An implementation of the OSGi R4.3 HTTP service.</li>
<li>HTTP Servlet - Generic support for exposing another servlet facility (e.g., an underlying application server) as an OSGi HTTP service.</li>
<li>IO Connector Service - An implementation of the OSGi R4.3 IO Connector Service.</li>
<li>Initial Provisioning - An implementation of the OSGi R4.3 Initial Provisioning.</li>
<li>Log Service - An implementation of the OSGi R4.3 Log service.</li>
<li>Metatype Service - An implementation of the OSGi R4.3 Metatype service.</li>
<li>Preferences Service - The Eclipse preference service is an extension of the standard OSGi preference service that adds listeners and the notion of preference scopes.</li>
<li>User Admin Service - An implementation of the OSGi R4.3 User Admin Service.</li>
<li>Wire Admin Service - An implementation of the OSGi R4.3 Wire Admin Service.</li>
</ul>
</li>
<li><b>p2</b>
<ul>
<li>Command line application to mirror repositories.</li>
<li>Command line application to manage (install / uninstall / update) an eclipse install.</li>
<li>UI to manage an eclipse installation from within eclipse.</li>
<li>API to programmatically interact with p2.</li>
</ul>
</li>
<li><b>Component model</b>
<ul>
<li>Eclipse Extension Registry - The Eclipse extension registry allows bundles to communicate and cooperate using declarative markup and lazy instantiation.</li>
<li>Equinox Transforms - A framework to provide transformations of bundle resources.</li>
</ul>
</li>
<li><b>Security</b>
<ul>
<li>Equinox Secure Storage</li>
<li>Certificate Trust Engine - API for to managing trusted certificates</li>
</ul>
</li>
<li><b>Server Side</b>
<ul>
<li>HTTP Registry - Support for registering servlets, resources and JSPs via the Eclipse extension registry rather than using the code based OSGi registration mechanisms.</li>
<li>JSP Registry - Provides a JSP Factory that allows JSP usage with the HTTP Registry.</li>
<li>Servlet Bridge - Low level hook servlet installed in an existing traditional application server. This servlet launches an embedded Equinox and enables it to handle incoming HTTP requests originally sent to the underlying server.</li>
<li>HTTP Jetty - A thin layer that exposes an embedded Jetty server as a compliant OSGi HTTP service.</li>
</ul>
</li>
<li><b>Weaving</b>
<ul>
<li>Equinox Weaving - Support for weaving aspects at runtime.</li>
</ul>
</li>
</ul>
</div><p><a href="#toc">Table of Contents</a></p><h2><a name="release_milestones">Release Milestones</a></h2><p>
Release milestones will be occurring at roughly 6 week intervals, and will be aligned with the
<a href="http://wiki.eclipse.org/Indigo_Simultaneous_Release">
Indigo Simultaneous Release</a> train.</p><table border="1" align="center"><tr><td><b>M1</b></td><td>08/06/2010</td><td><div>3.7M1</div></td></tr><tr><td><b>M2</b></td><td>09/17/2010</td><td><div>3.7M2</div></td></tr><tr><td><b>M3</b></td><td>10/29/2010</td><td><div>3.7M3</div></td></tr><tr><td><b>M4</b></td><td>12/10/2010</td><td><div>3.7M4</div></td></tr><tr><td><b>M5</b></td><td>01/28/2011</td><td><div>3.7M5</div></td></tr><tr><td><b>M6</b></td><td>03/11/2011</td><td><div>3.7M6 (API Freeze)</div></td></tr><tr><td><b>M7</b></td><td>04/29/2011</td><td><div>3.7M7 (Feature Freeze)</div></td></tr></table><div>
<p>Individual, milestone level plans for the components that make up the Equinox Project can be found
on the <a href="http://wiki.eclipse.org/Equinox/Plan/Indigo">Equinox Project Indigo Plan page</a>
on the Equinox wiki.</p>
<p>Our target is to complete 3.7 in late June 2011, in alignment with Indigo.
All release deliverables will be available for download as soon as the release has been
tested and validated in the target operating configurations listed below.</p>
<p>Dates for builds and test passes after M7 will be available in the
Equinox Indigo end-game plan, available shortly before M7 in April 2011.
</p>
</div><p><a href="#toc">Table of Contents</a></p><h2><a name="target_environments">Target Environments</a></h2><div>
<p>In order to remain current, each Equinox Project release targets reasonably current
operating environments.</p>
<p>Most of Equinox is "pure" Java code and has no direct dependence
on the underlying operating system. The chief dependence is therefore on the
Java Platform itself. Portions are targeted to specific classes of operating
environments, requiring their source code to only reference facilities available
in particular class libraries (e.g. J2ME Foundation 1.1, J2SE 1.4, Java 5, etc).</p>
<p>In general, the 3.7 release of the Equinox Project is developed on a mix
of Java 1.4, SE 5 and Java SE 6 VMs. As such, the Equinox SDK as a whole
is targeted at all modern, desktop Java VMs. Most functionality is available for
1.4 level development everywhere, and extended development capabilities are made
available on the VMs that support them.</p>
<p><a href="#Appendix1">Appendix 1</a> contains a table that indicates the class
library level required for each bundle.</p>
<p>There are many different implementations of the Java Platform running atop
a variety of operating systems. We focus our testing on a handful of
popular combinations of operating system and Java Platform; these are our <em>reference
platforms</em>. Equinox undoubtedly runs fine in many operating environments
beyond the reference platforms we test. However, since we do not systematically test
them we cannot vouch for them. Problems encountered when running Equinox on a
non-reference platform that cannot be recreated on any reference platform will
be given lower priority than problems with running Eclipse on a reference platform.</p>
<p>Equinox 3.7 is tested and validated on the following reference platforms
(this list is updated over the course of the release cycle):</p>
<style type="text/css">
table.platforms {
border-width: 1px;
border-spacing: 0px;
border-style: solid;
border-collapse: separate;
}
table.platforms th {
border-width: 1px;
padding: 3px;
border-style: inset;
border-color: black;
background-color: #B9A9FF;
}
table.platforms td {
border-width: 1px 1px 1px 1px;
padding: 3px 3px 3px 3px;
border-style: inset inset inset inset;
border-color: gray gray gray gray;
}
table.platforms tr.c0 td {
background-color: #FDFDFD;
}
table.platforms tr.c1 td {
background-color: #F4EEFF;
}
</style>
<table class="platforms">
<tr>
<th>Operating System</th>
<th>Version</th>
<th>Hardware</th>
<th>JRE</th>
<th>Windowing System</th>
</tr>
<tr class="c0">
<td rowspan="6">Windows</td>
<td rowspan="2">7</td>
<td rowspan="1">x86 32-bit</td>
<td rowspan="6">Sun Java 6 Update 17<br/>
IBM Java 6 SR8
</td>
<td rowspan="6">Win32</td>
</tr>
<tr>
<td rowspan="1">x86 64-bit</td>
</tr>
<tr>
<td rowspan="2">Vista</td>
<td rowspan="1">x86 32-bit</td>
</tr>
<tr class="c0">
<td rowspan="1">x86 64-bit</td>
</tr>
<tr class="c0">
<td rowspan="2">XP</td>
<td rowspan="1">x86 32-bit</td>
</tr>
<tr class="c0">
<td rowspan="1">x86 64-bit</td>
</tr>
<tr class="c1">
<td rowspan="3">Red Hat Enterprise Linux</td>
<td rowspan="2">5.0</td>
<td rowspan="1">x86 32-bit</td>
<td>Sun Java 6 Update 17<br/>
IBM Java 6 SR8
</td>
<td rowspan="3">GTK</td>
</tr>
<tr class="c1">
<td rowspan="1">Power 64-bit</td>
<td>IBM Java 6 SR8</td>
</tr>
<tr class="c1">
<td rowspan="1">4.0</td>
<td rowspan="1">x86 64-bit</td>
<td>Sun Java 6 Update 17<br/>
IBM Java 6 SR8
</td>
</tr>
<tr class="c0">
<td rowspan="3">SUSE Linux Enterprise Server</td>
<td rowspan="3">11</td>
<td rowspan="1">x86 32-bit</td>
<td rowspan="2">Sun Java 6 Update 17<br/>
IBM Java 6 SR8
</td>
<td rowspan="3">GTK</td>
</tr>
<tr class="c0">
<td rowspan="1">x86 64-bit</td>
</tr>
<tr class="c0">
<td rowspan="1">Power 64-bit</td>
<td>IBM Java 6 SR8</td>
</tr>
<tr class="c1">
<td rowspan="2">Ubuntu Long Term Support</td>
<td rowspan="2">10.04</td>
<td rowspan="1">x86 32-bit</td>
<td rowspan="2">Sun Java 6 Update 17<br/>
IBM Java 6 SR8
</td>
<td rowspan="2">GTK</td>
</tr>
<tr class="c1">
<td rowspan="1">x86 64-bit</td>
</tr>
<tr class="c0">
<td rowspan="2">Sun Solaris</td>
<td rowspan="2">10</td>
<td rowspan="1">x86 32-bit</td>
<td rowspan="2">Sun Java 6 Update 17</td>
<td rowspan="2">GTK</td>
</tr>
<tr class="c0">
<td rowspan="1">SPARC 32-bit</td>
</tr>
<tr class="c1">
<td rowspan="1">HP-UX</td>
<td rowspan="1">11i v2</td>
<td rowspan="1">ia64 32-bit</td>
<td rowspan="1">HP-UX Java 5 Update 18</td>
<td rowspan="1">Motif 2.1</td>
</tr>
<tr class="c0">
<td rowspan="1">IBM AIX</td>
<td rowspan="1">5.3</td>
<td rowspan="1"><img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/> Power 64-bit</td>
<td rowspan="1">IBM Java 6 SR8</td>
<td rowspan="1"><img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/> GTK</td>
</tr>
<tr class="c1">
<td rowspan="3">Apple Mac OS X</td>
<td rowspan="3"><img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/> 10.6</td>
<td rowspan="1"><img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/> <s>Universal</s></td>
<td rowspan="3"><img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/> Apple Java 10.6 Update 2</td>
<td rowspan="1"><img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/> <s>Carbon</s></td>
</tr>
<tr class="c1">
<td rowspan="1">Universal 32-bit</td>
<td rowspan="2">Cocoa</td>
</tr>
<tr class="c1">
<td rowspan="1">Universal 64-bit</td>
</tr>
</table>
<p>As stated above, <i>we expect that Equinox works fine on other current
Java VM and OS versions but we cannot flag these as reference platforms without
significant community support for testing them.</i></p>
</div><h3>Internationalization</h3>
<p>The Equinox SDK is designed as the basis for internationalized products. The
user interface elements provided by the Equinox components, including dialogs
and error messages, are externalized. The English strings are provided as the
default resource bundles.</p>
<p>Latin-1 and DBCS locales are supported by the Equinox on all reference platforms;
BIDI locales are supported by the Equinox everywhere but on Motif.</p>
<p>The Equinox supports GB 18030 (level 1), the Chinese code page standard,
on Windows XP and 2000, Linux/GTK and the Macintosh.</p>
<p>German and Japanese locales are tested.</p>
<p><a href="#toc">Table of Contents</a></p><h2><a name="compatibility">Compatibility with Previous Releases</a></h2><div>
<h3>Compatibility of Release 3.7 with 3.6</h3>
<p>Equinox 3.7 will be compatible with Equinox 3.6 (and all earlier 3.x versions).</p>
<p><strong>API Contract Compatibility:</strong> Equinox 3.7 will be upwards
contract-compatible with Equinox 3.6 except in those areas noted in the
<a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_7_porting_guide.html" target="_top">
<em>Eclipse 3.7 Plug-in Migration Guide</em>
</a>. Programs that use affected APIs and extension points will need to be ported
to Equinox 3.7 APIs. Downward contract compatibility
is not supported. There is no guarantee that compliance with Equinox 3.7
APIs would ensure compliance with Equinox 3.6 APIs. Refer to
<a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">
<em>Evolving Java-based APIs</em>
</a> for a discussion of the kinds of API changes that maintain contract compatibility.</p>
<p><strong>Binary (plug-in) Compatibility:</strong> Equinox 3.7 will be upwards
binary-compatible with Equinox 3.6 except in those areas noted in the
<a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_7_porting_guide.html" target="_top">
<em>Eclipse 3.7 Plug-in Migration Guide</em>
</a>. Downward plug-in compatibility is not supported. Plug-ins for Equinox
3.7 will not be usable in Equinox 3.6. Refer to
<a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">
<em>Evolving Java-based APIs</em>
</a> for a discussion of the kinds of API changes that maintain binary compatibility.</p>
<p><strong>Source Compatibility:</strong> Equinox 3.7 will be upwards source-compatible
with Equinox 3.6 except in the areas noted in the
<a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_7_porting_guide.html" target="_top">
<em>Eclipse 3.7 Plug-in Migration Guide</em>
</a>. This means that source files written
to use Equinox 3.6 APIs might successfully compile and run against Equinox
3.7 APIs, although this is not guaranteed. Downward source compatibility
is not supported. If source files use new Equinox APIs, they will not be
usable with an earlier version of Equinox. </p>
<p><strong>Workspace Compatibility:</strong> Equinox 3.7 will be upwards
workspace-compatible with earlier 3.x versions of the Equinox unless noted.
This means that workspaces and projects created with Equinox 3.6 .. 3.0 can be successfully
opened by Equinox 3.7 and upgraded to a 3.7 workspace. This includes both
hidden metadata, which is localized to a particular workspace, as well as metadata
files found within a workspace project (e.g., the .project file), which may
propagate between workspaces via file copying or team repositories. Individual
plug-ins developed for Eclipse SDK 3.7 should provide similar upwards compatibility
for their hidden and visible workspace metadata created by earlier versions;
3.7 plug-in developers are responsible for ensuring that their plug-ins recognize
metadata from earlier versions and process it appropriately. User
interface session state may be discarded when a workspace is upgraded. Downward
workspace compatibility is not supported. A workspace created (or opened) by
a product based on Eclipse 3.7 will be unusable with a product based on an earlier
version of Eclipse. Visible metadata files created (or overwritten) by Eclipse
3.7 will generally be unusable with earlier versions of Eclipse. </p>
<p><strong>Non-compliant usage of API's</strong>: All non-API methods and classes,
and certainly everything in a package with "internal" in its name or
exported with the x-internal directive,
are considered implementation details which may vary between operating environment
and are subject to change without notice. Client plug-ins that directly depend
on anything other than what is specified in the Equinox API are inherently
unsupportable and receive no guarantees about compatibility within a single
release much less with earlier releases. Refer to
<a href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">
<em>How to Use the Eclipse API</em>
</a> for information about how to write compliant plug-ins. </p>
</div><p><a href="#toc">Table of Contents</a></p><h2><a name="themes_and_priorities">Themes and Priorities</a></h2><div>
<p>The plan items listed below were defined according to contributor requirements and the Eclipse
<a href="http://wiki.eclipse.org/RequirementsCouncilThemesAndPriorities">Themes and Priorities</a>
set forth by the Eclipse Requirements Council. Each plan item covers a feature or API that is
to be added to the Equinox Project deliverables, or some aspect of the Equionx Project that is
to be improved. Each plan item has its own entry in the Equinox bugzilla database, with a title
and a concise summary (usually a single paragraph) that explains the work item at a suitably
high enough level so that everyone can readily understand what the work item entails.</p>
<p> Although there are several components under the Equinox Project, there
is a significant amount of commonality and shared effort between them. In general,
many plan items involve coordinated changes to multiple components, and thus
attempting to separate the items into sections based on components leads to
artificial distinctions between them (e.g., Framework vs. p2, Compendium vs Server Side, etc.)
As such, this plan covers the work of all projects under the Equinox Project.</p>
<p>Not all plan items represent the same amount of work; some may be quite
large, others, quite small. Although some plan items are for work that is
more pressing than others, the plan items appear in no particular order.
See the corresponding bugzilla items for up-to-date status information on
ongoing work and planned delivery milestones.</p>
<p>The current status of each plan item is noted:</p>
<ul>
<li><b>Committed</b> plan item - A committed plan item is one that we have
decided to address for the release. In bugzilla, this is reflected by
having a concrete target milestone assigned.</li>
<li><b>Proposed</b> plan item - A proposed plan item is one that we are
considering addressing for the release. Although we are actively
investigating it, we are not yet in a position to commit to it, or to say
that we won't be able to address it. After due consideration, a proposal
will either be committed or deferred. In bugzilla, such items are reflected
by having a target milestone "3.7" or "---" assigned.</li>
<li><b>Deferred</b> plan item - A reasonable proposal that will not make it in
to this release for some reason is marked as deferred with a brief note as
to why it was deferred. Deferred plan items may resurface as committed plan
items at a later point. In bugzilla, such items are reflected by having
a target milestone "---" assigned.</li>
</ul>
</div><h3>Scalability and Performance</h3><p>New usage scenarios for Equinox require it to be faster, smaller, bigger, ...
The technology needs to scale up or down to allow Equinox to scale down to small embedded environments as well
as scaling up to large server environments.
Monitor overall performance and memory consumption which includes the addition of new performance tests for new features.
</p><ul><li><b>Committed</b><p><i>None at this time.</i></p></li></ul><ul><li><b>Proposed</b><ul>
<li>
<strong>Performance improvements in p2</strong>
Improvements will include, but are not limited to memory savings, speed
improvements and disk footprint.
Areas of focus will include the reconciler, dealing with large repositories and
a large number of repositories (specifically composite repositories), UI
updates, metadata repository size on disk, etc.
[p2] (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=333894">333894</a>)
</li>
</ul></li></ul><ul><li><b>Deferred</b><p><i>None at this time.</i></p></li></ul><h3>Robustness</h3><p>As the basis for the entire Eclipse eco-system, Equinox must be robust,
flexible and secure. This work will address those issues by providing API for
missing or currently internal functionality, and focusing on the issues that
affect the stability of the platform.
</p><ul><li><b>Committed</b><p><i>None at this time.</i></p></li></ul><ul><li><b>Proposed</b><ul>
<li><img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/>
<strong>Support for elevated privileges for updates in shared install</strong>
Typically when installing an appliction on Windows 7 in Program Files,
special privileges are required. In most installers (e.g. MSI) this is done via
privileges elevation. So one part of application runs with current user
privileges and other part with system user privileges. This requires almost no
effort from the user. For the Indigo release, investigation will be done to
see if we can seemlessly use use elevated privileges when installing updates with p2.
[p] (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=322477">322477</a>)
</li>
</ul></li></ul><ul><li><b>Deferred</b><p><i>None at this time.</i></p></li></ul><h3>Consumability</h3><p>This work will make it easier for users to get Equinox, install it on their systems,
and configure it for their use. It also covers work related to error handling and reporting
mechanisms.
</p><ul><li><b>Committed</b><ul>
<li><img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/>
<strong>Consolidate and unify the eclipse logging APIs</strong>
The eclipse platform and equinox have several logging APIs both public and internal. Public
logging API includes the FrameoworkLog, ILog and the OSGi LogService. The various logging APIs
in eclipse will be unified by using the Equinox Extended OSGi LogService. This will allow a log
listener to listen for log events from any bundle no matter what eclipse logging API was used to
log the message.
[framework] (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=292135">292135</a>)
</li>
</ul></li></ul><ul><li><b>Proposed</b><p><i>None at this time.</i></p></li></ul><ul><li><b>Deferred</b><p><i>None at this time.</i></p></li></ul><h3>Future</h3><p>Eclipse is evolving quickly. New features in the next OSGi specification and e4 will drive numerous changes throughout the Equinox
project. Considerable effort will be put into updating Equinox to accomodate and exploit these new scenarios.
</p><ul><li><b>Committed</b><ul>
<li><img src="http://www.eclipse.org/eclipse/development/new.gif" alt="(new)" border="0" height="12" width="12"/>
<strong>Participate in the OSGi specification process</strong>
Various OSGi specifications are actively being developed by the OSGi Alliance. Equinox will
participate in the specification process to provide our expertise in areas that apply to Equinox.
In many cases Equinox will provide an implementation of the new specification if the specification
schedule aligns with the Equinox release schedule and we have Equinox community interest.
[All Components] (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=289124">289124</a>)
</li>
</ul></li></ul><ul><li><b>Proposed</b><p><i>None at this time.</i></p></li></ul><ul><li><b>Deferred</b><p><i>None at this time.</i></p></li></ul><p><a href="#toc">Table of Contents</a></p><h2><a name="appendix">Appendix Execution Environment by Bundle</a></h2><p>In the table below, the "3.7 minimum execution environment"
column indicates the minimum Java class library requirements of each bundle
for the 3.7 release, where the value is one of:</p><table border="0" width="90%">
<tr>
<td align="center"><b>Entry</b></td>
<td align="left"><b>Meaning</b></td>
</tr>
<tr>
<td><div align="center"><strong>M1.0</strong></div></td>
<td>OSGi Minimum Execution Environment 1.0 - This is a subset of the J2ME
Foundation 1.0 class libraries defined by OSGi to be the base for framework
implementations. See the OSGi specification for more details.</td>
</tr>
<tr>
<td width="9%"><div align="center"><strong>M1.1</strong></div></td>
<td width="91%">OSGi Minimum Execution Environment 1.1 - This is a subset
of the J2ME Foundation 1.1 class libraries defined by OSGi to be the base
for framework implementations. See the OSGi specification for more details.</td>
</tr>
<tr>
<td width="9%"><div align="center"><strong>M1.2</strong></div></td>
<td width="91%">OSGi Minimum Execution Environment 1.2 - This is a subset
of the J2ME Foundation 1.1 class libraries defined by OSGi to be the base
for framework implementations. See the OSGi specification for more details.</td>
</tr>
<tr>
<td><div align="center"><strong>F1.0</strong></div></td>
<td>J2ME Foundation 1.0 - indicates that the bundle can only be run on
Foundation 1.0 or greater. Note that with the exception of some MicroEdition
IO classes, Foundation 1.0 is a subset of J2SE 1.3.</td>
</tr>
<tr>
<td><div align="center"><strong>F1.1</strong></div></td>
<td>J2ME Foundation 1.1 - indicates that the bundle can only be run on
Foundation 1.1 or greater. Note that with the exception of some MicroEdition
IO classes, Foundation 1.1 is a subset of J2SE 1.4.</td>
</tr>
<tr>
<td><div align="center"><strong>1.3</strong></div></td>
<td>J2SE 1.3 - indicates that the bundle can only be run on JSE 1.3 or
greater.</td>
</tr>
<tr>
<td><div align="center"><strong>1.4</strong></div></td>
<td>J2SE 1.4 - indicates that the bundle can only be run on JSE 1.4 or
greater.</td>
</tr>
<tr>
<td><div align="center"><strong>1.5</strong></div></td>
<td>Java SE 5 - indicates that the bundle can only be run on Java SE 5 or
greater.</td>
</tr>
<tr>
<td><div align="center"><strong>1.6</strong></div></td>
<td>Java SE 6 - indicates that the bundle can only be run on Java SE 6 or
greater.</td>
</tr>
<tr>
<td align="center"><b>n/a</b></td>
<td>Unknown at the time of this revision.</td>
</tr>
</table><p><b>Table of minimum execution environments by bundle.</b> (See also the
<a href="http://www.eclipse.org/projects/project-plan.php?projectid=rt.equinox#appendix">Equinox Project plan</a>
for the execution environment requirements of bundles contributed via that project.)</p><table border="1">
<tr>
<td width="290"><strong>Bundle</strong></td>
<td width="60"><div align="center"><p align="center"><b>3.7<br/>minimum<br/>execution<br/>environment</b></p></div></td>
</tr>
<tr>
<td>org.eclipse.equinox.app</td>
<td><div align="center">M1.2</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.cm</td>
<td><div align="center">M1.2</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.common</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.concurrent</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.device</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.ds</td>
<td><div align="center">M1.2</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.event</td>
<td><div align="center">M1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.frameworkadmin</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.frameworkadmin.equinox</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.http</td>
<td><div align="center">M1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.http.jetty</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.http.registry</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.http.servlet</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.http.servletbridge</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.io</td>
<td><div align="center">M1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.ip</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.jsp.jasper</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.jsp.jasper.registry</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher</td>
<td><div align="center">M1.2</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.carbon.macosx</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.cocoa.macosx</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.cocoa.macosx.x86_64</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.gtk.linux.ppc</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.gtk.linux.s390</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.gtk.linux.s390x</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.gtk.linux.x86</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.gtk.linux.x86_64</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.gtk.solaris.sparc</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.gtk.solaris.x86</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.motif.aix.ppc</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.motif.hpux.PA_RISC</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.motif.hpux.ia64_32</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.motif.linux.x86</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.motif.solaris.sparc</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.win32.win32.ia64</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.win32.win32.x86</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.win32.win32.x86_64</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.launcher.wpf.win32.x86</td>
<td><div align="center">N/A</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.log</td>
<td><div align="center">M1.2</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.metatype</td>
<td><div align="center">M1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.artifact.repository</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.console</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.core</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.director</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.director.app</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.directorywatcher</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.engine</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.exemplarysetup</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.extensionlocation</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.garbagecollector</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.jarprocessor</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.metadata</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.metadata.generator</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.metadata.repository</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.publisher</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.reconciler.dropins</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.repository</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.repository.tools</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.touchpoint.eclipse</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.touchpoint.natives</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.ui</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.ui.sdk</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.ui.sdk.scheduler</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.updatechecker</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.p2.updatesite</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.preferences</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.registry</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.security</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.security.macosx</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.security.tests</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.security.ui</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.security.win32.x86</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.servletbridge</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.simpleconfigurator</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.simpleconfigurator.manipulator</td>
<td><div align="center">F1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.supplement</td>
<td><div align="center">F1.0</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.transforms.hook</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.transforms.xslt</td>
<td><div align="center">1.4</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.useradmin</td>
<td><div align="center">M1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.util</td>
<td><div align="center">M1.1</div></td>
</tr>
<tr>
<td>org.eclipse.equinox.wireadmin</td>
<td><div align="center">M1.0</div></td>
</tr>
<tr>
<td>org.eclipse.osgi</td>
<td><div align="center">M1.2</div></td>
</tr>
<tr>
<td>org.eclipse.osgi.services</td>
<td><div align="center">M1.2</div></td>
</tr>
<tr>
<td>org.eclipse.osgi.util</td>
<td><div align="center">M1.2</div></td>
</tr>
</table><p><a href="#toc">Table of Contents</a></p></div>
</div>
</div>
<div style="float: right; text-align: right"><a href="?projectid=rt.equinox&raw=1">view raw xml of project plan</a><br>
<a href="/projects/dev_process/project-status-infrastructure.php">from project meta-data key "projectplanurl"</a></div>
</div> <!-- midcolumn -->
</div> <!-- fullcolumn -->
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-910670-2']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
<br style="clear:both;height:1em;"/>&nbsp;
</div>
<div id="clearFooter"></div>
<div id="footer">
<ul id="footernav">
<li><a href="/">Home</a></li>
<li><a href="/legal/privacy.php">Privacy Policy</a></li>
<li><a href="/legal/termsofuse.php">Terms of Use</a></li>
<li><a href="/legal/copyright.php">Copyright Agent</a></li>
<li><a href="/legal/">Legal</a></li>
<li><a href="/org/foundation/contact.php">Contact Us</a></li>
</ul>
<span id="copyright">Copyright &copy; 2011 The Eclipse Foundation. All Rights Reserved.</span>
</div>
</div> </body>
</html>