blob: d7942f60935007c29099c714f3b23b93c604ea08 [file] [log] [blame]
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns:x="urn:schemas-microsoft-com:office:excel"
xmlns:p="urn:schemas-microsoft-com:office:powerpoint"
xmlns:a="urn:schemas-microsoft-com:office:access"
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882"
xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema"
xmlns:b="urn:schemas-microsoft-com:office:publisher"
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet"
xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet"
xmlns:oa="urn:schemas-microsoft-com:office:activation"
xmlns:html="http://www.w3.org/TR/REC-html40"
xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:"
xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml"
xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/"
xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp"
xmlns:udc="http://schemas.microsoft.com/data/udc"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile"
xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 11">
<meta name=Originator content="Microsoft Word 11">
<link rel=File-List href="mdt_project_plan_1_1_files/filelist.xml">
<link rel=Edit-Time-Data href="mdt_project_plan_1_1_files/editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>DRAFT Eclipse MDT - 1.1 Plan</title>
<!--[if gte mso 9]><xml>
<o:DocumentProperties>
<o:Author>khussey</o:Author>
<o:Template>Normal</o:Template>
<o:LastAuthor>Kenn Hussey</o:LastAuthor>
<o:Revision>141</o:Revision>
<o:TotalTime>4083</o:TotalTime>
<o:Created>2004-10-27T01:51:00Z</o:Created>
<o:LastSaved>2007-10-22T14:21:00Z</o:LastSaved>
<o:Pages>1</o:Pages>
<o:Words>5101</o:Words>
<o:Characters>29081</o:Characters>
<o:Company>IBM</o:Company>
<o:Lines>242</o:Lines>
<o:Paragraphs>68</o:Paragraphs>
<o:CharactersWithSpaces>34114</o:CharactersWithSpaces>
<o:Version>11.8132</o:Version>
</o:DocumentProperties>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:Compatibility>
<w:ApplyBreakingRules/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
</w:LatentStyles>
</xml><![endif]-->
<link rel=Stylesheet type="text/css" media=all href="default_style.css">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;
mso-font-alt:"\FF2D\FF33 \660E\671D";
mso-font-charset:128;
mso-generic-font-family:roman;
mso-font-format:other;
mso-font-pitch:fixed;
mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:536871559 0 0 0 415 0;}
@font-face
{font-family:"\@MS Mincho";
mso-font-charset:128;
mso-generic-font-family:modern;
mso-font-pitch:fixed;
mso-font-signature:-1610612033 1757936891 16 0 131231 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";
mso-believe-normal-left:yes;}
h1
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
mso-outline-level:1;
font-size:21.0pt;
mso-fareast-font-family:"MS Mincho";
font-weight:bold;}
h2
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-line-height-alt:10.5pt;
mso-pagination:widow-orphan;
mso-outline-level:2;
font-size:18.0pt;
mso-fareast-font-family:"MS Mincho";
font-weight:bold;}
h3
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
mso-outline-level:3;
font-size:14.0pt;
mso-fareast-font-family:"MS Mincho";
font-weight:bold;}
h4
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
mso-outline-level:4;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"MS Mincho";
font-weight:bold;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;
text-underline:single;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:10.0pt;
mso-fareast-font-family:"Times New Roman";}
code
{mso-fareast-font-family:"Times New Roman";}
pre
{margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
font-size:10.0pt;
mso-fareast-font-family:"Times New Roman";}
p.indextop, li.indextop, div.indextop
{mso-style-name:indextop;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:24.0pt;
mso-fareast-font-family:"Times New Roman";
font-weight:bold;}
p.indexsub, li.indexsub, div.indexsub
{mso-style-name:indexsub;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:7.5pt;
mso-fareast-font-family:"Times New Roman";}
p.jump, li.jump, div.jump
{mso-style-name:jump;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:10.0pt;
mso-fareast-font-family:"Times New Roman";}
span.header
{mso-style-name:header;}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:199630218;
mso-list-template-ids:-1221184516;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:213278280;
mso-list-template-ids:1664226462;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:676233000;
mso-list-template-ids:-227133684;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:1150950361;
mso-list-template-ids:931181238;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4
{mso-list-id:1303848377;
mso-list-template-ids:-391109514;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5
{mso-list-id:1613197431;
mso-list-template-ids:-1199681340;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l6
{mso-list-id:1823885605;
mso-list-template-ids:-2006171628;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l7
{mso-list-id:1908878861;
mso-list-template-ids:-1221573220;}
@list l7:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
</style>
<![endif]--><![if mso 9]>
<style>
p.MsoNormal
{margin-left:8.5pt;}
</style>
<![endif]>
<meta name="Kenn Hussey" content="Eclipse UML2 PMC">
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="30722"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1"/>
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=blue style='tab-interval:.5in;margin-left:
8.5pt;margin-top:14.2pt'>
<div class=Section1>
<h1>DRAFT Eclipse MDT<br>
1.1 Plan</h1>
<p>Last revised 10:20 EDT October 22, 2007 (<img width=12 height=12
id="_x0000_i1025" src="../../images/new.gif" border=0> marks interesting
changes over the <i style='mso-bidi-font-style:normal'><a
href="mdt_project_plan_1_1_20071004.html">previous plan revision</a></i>)</p>
<p><i>Please send comments about this plan to the </i><a
href="mailto:mdt-dev@eclipse.org">mdt-dev@eclipse.org</a> <i>developer mailing
list.</i></p>
<p>This document lays out the feature and API set for the next feature release
of the Eclipse MDT project, designated release 1.1. </p>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_Release_deliverables">Release deliverables</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_Release_milestones">Release milestones</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_Target_Operating_Environments">Target
operating environments</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_Compatibility_with_Previous">Compatibility
with previous releases</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_EODM_component">EODM component</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_OCL_component">OCL component</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_OCL_Tools_component">OCL Tools component</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_UML2_component">UML2 component</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_UML2_Tools_component">UML2 Tools component</a><o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'><a href="#_XSD_component">XSD component</a><o:p></o:p></span></li>
</ul>
<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, plans are posted in an embryonic form and then revised from time to
time 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.&nbsp; </p>
<p>The remainder of the plan consists of plan items for the components under
the Eclipse MDT project. Each plan item covers a feature or API that is to be
added, or some aspect that is to be improved. Each plan item has its own entry
in the Eclipse <span class=SpellE>bugzilla</span> 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 subsystem; others may involve coordinated changes across several
projects within the same top-level project; and others may involve coordination
with other top-level projects. Although some plan items are for work that is
more pressing that others, the plan items appear in no particular order. </p>
<p>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 type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><b style='mso-bidi-font-weight:
normal'><span style='font-size:10.0pt;font-family:Arial'>Committed</span></b><span
style='font-size:10.0pt;font-family:Arial'> plan item – A committed plan
item is one that we have decided to address for the release.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><b style='mso-bidi-font-weight:
normal'><span style='font-size:10.0pt;font-family:Arial'>Proposed</span></b><span
style='font-size:10.0pt;font-family:Arial'> 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.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l1 level1 lfo3;tab-stops:list .5in'><b style='mso-bidi-font-weight:
normal'><span style='font-size:10.0pt;font-family:Arial'>Deferred</span></b><span
style='font-size:10.0pt;font-family:Arial'> plan item – A reasonable
proposal that will not make it into 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.<o:p></o:p></span></li>
</ul>
<h2><a name="_Release_deliverables"></a>Release deliverables</h2>
<p>The release deliverables are: </p>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>Source code release for the EODM component, available
as versions tagged &quot;R1_0&quot; in the eclipse.org <a
href="http://dev.eclipse.org/viewcvs/">CVS repository</a>.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>EODM runtime binary and SDK distributions
(downloadable).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>EODM runtime binary and SDK features on eclipse.org
update site (install via Eclipse update manager).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>Source code release for the OCL component, available as
versions tagged &quot;R1_2&quot; in the eclipse.org <a
href="http://dev.eclipse.org/viewcvs/">CVS repository</a>.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>OCL runtime binary and SDK distributions
(downloadable).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>OCL runtime binary and SDK features on eclipse.org
update site (install via Eclipse update manager).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>Source code release for the OCL Tools component,
available as versions tagged &quot;R0_7&quot; in the eclipse.org <a
href="http://dev.eclipse.org/viewcvs/">CVS repository</a>.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>OCL Tools runtime binary and SDK distributions
(downloadable).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>OCL Tools runtime binary and SDK features on
eclipse.org update site (install via Eclipse update manager).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>Source code release for the UML2 component, available
as versions tagged &quot;R2_2&quot; in the eclipse.org <a
href="http://dev.eclipse.org/viewcvs/">CVS repository</a>.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>UML2 runtime binary and SDK distributions (downloadable).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>UML2 runtime binary and SDK features on eclipse.org
update site (install via Eclipse update manager).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>Source code release for the UML2 Tools component,
available as versions tagged &quot;R0_8&quot; in the eclipse.org <a
href="http://dev.eclipse.org/viewcvs/">CVS repository</a>.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>UML2 Tools runtime binary and SDK distributions
(downloadable).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>UML2 Tools runtime binary and SDK features on
eclipse.org update site (install via Eclipse update manager).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>Source code release for XSD component, available as
versions tagged &quot;R2_4&quot; in the eclipse.org <a
href="http://dev.eclipse.org/viewcvs/">CVS repository</a>.<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>XSD runtime binary and SDK distributions
(downloadable).<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l2 level1 lfo7;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>XSD runtime binary and SDK features on eclipse.org
update site (install via Eclipse update manager).<o:p></o:p></span></li>
</ul>
<h2><a name="_Release_milestones"></a>Release milestones</h2>
<p>Release milestone occurring at roughly 6 week intervals exist to facilitate
coarse-grained planning and staging. The milestones are:</p>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo11;tab-stops:list .5in'><img border=0 width=12
height=12 id="_x0000_i1033" src="../../images/new.gif"><span
style='font-size:10.0pt;font-family:Arial'>Wednesday, October 3 –
Milestone 2 (1.1 M2) – Stable Build based on Eclipse 3.4 M2<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo11;tab-stops:list .5in'><img border=0 width=12
height=12 id="_x0000_i1034" src="../../images/new.gif"><span
style='font-size:10.0pt;font-family:Arial'>Wednesday, November 14 –
Milestone 3 (1.1 M3) – Stable Build based on Eclipse 3.4 M3<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo11;tab-stops:list .5in'><img border=0 width=12
height=12 id="_x0000_i1035" src="../../images/new.gif"><span
style='font-size:10.0pt;font-family:Arial'>Wednesday, January 9 –
Milestone 4 (1.1 M4) – Stable Build based on Eclipse 3.4 M4<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo11;tab-stops:list .5in'><img border=0 width=12
height=12 id="_x0000_i1036" src="../../images/new.gif"><span
style='font-size:10.0pt;font-family:Arial'>Wednesday, February 20 –
Milestone 5 (1.1 M5) –Stable Build based on Eclipse 3.4 M5<o:p></o:p></span></li>
</ul>
<p>The 1.1 release is targeted for late June 2008. 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>
<h2><a name="_Target_Operating_Environments"></a>Target Operating Environments</h2>
<p>In order to remain current, each release of an Eclipse project targets
reasonably current versions of underlying operating environments and other
Eclipse projects on which it depends.&nbsp;</p>
<p>Most of Eclipse is &quot;pure&quot; <span class=SpellE>Java<sup><span
style='font-size:9.5pt'>TM</span></sup></span> code and has no direct
dependence on the underlying operating system. The chief dependence is on the
Eclipse Platform, and on the Java 2 Platform that runs it.</p>
<p>The MDT 1.1 release depends on the following:</p>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l4 level1 lfo10;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>Java 2 Platform 1.5<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l4 level1 lfo10;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>Eclipse Platform 3.4<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l4 level1 lfo10;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>EMF 2.4<o:p></o:p></span></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l4 level1 lfo10;tab-stops:list .5in'><span style='font-size:10.0pt;
font-family:Arial'>GMF 2.1<o:p></o:p></span></li>
</ul>
<p>The 1.1 release of MDT is designed to run on any configuration supporting
the above components.</p>
<p>The Eclipse Platform runs in a variety of operating environments. Testing is
focused on a handful of popular <span class=header>combinations of operating
system and Java 2 Platform; these are our </span><em><span style='font-family:
Arial'>reference platforms</span></em><span class=header>. Eclipse 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 Eclipse on 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.</span></p>
<p><span style='mso-bidi-font-weight:bold'>See the </span><img border=0
width=12 height=12 id="_x0000_i1037" src="../../images/new.gif"><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><a
href="http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_4.html">Eclipse
Project 3.4 plan</a></span></i><span style='mso-bidi-font-weight:bold'> for a
list of reference platforms.</span></p>
<h4><span style='font-family:Arial'>Internationalization<o:p></o:p></span></h4>
<p>Eclipse is designed as the basis for internationalized products. The user interface
elements provided by the various Eclipse projects, including dialogs and error
messages, are externalized. The English strings for MDT are provided as the
default resource bundles. Translations are not provided with this release.
However, the plug-in fragment mechanism provides the means by which
translations into any number of other languages can be incorporated.</p>
<h2><a name="_Compatibility_with_Previous"></a>Compatibility with Previous
Releases</h2>
<h3>Compatibility of EODM 1.0 with 0.9</h3>
<p>The EODM 1.0 component of Eclipse MDT will be compatible with EODM 0.9,
except in those areas noted in the <i style='mso-bidi-font-style:normal'>EODM
1.0 Migration Guide</i>.</p>
<p><b>API Contract Compatibility:</b> EODM 1.0 will be upwards
contract-compatible with EODM 0.9 except in those areas noted in the <i>EODM
1.0 Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>. Programs
that use affected APIs and extension points will need to be ported to EODM 1.0
APIs. Downward contract compatibility is not supported. There is no guarantee
that compliance with EODM 1.0 APIs would ensure compliance with EODM 0.9 APIs.
Refer to <i><a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving
Java-based APIs</a></i> for a discussion of the kinds of API changes that
maintain contract compatibility.</p>
<p><b>Binary (plug-in) Compatibility:</b> EODM 1.0 will be upwards
binary-compatible with EODM 0.9 except in those areas noted in the <i>EODM 1.0
Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>. Downward plug-in
compatibility is not supported: plug-ins compiled against EODM 1.0 will likely
be unusable with EODM 0.9. Refer to <i><a
href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving Java-based
APIs</a></i> for a discussion of the kinds of API changes that maintain binary
compatibility.</p>
<p><b>Source Compatibility:</b> Source files written to use EODM 0.9 APIs will
usually compile and run successfully against EODM 1.0 APIs, although this
cannot be guaranteed. In some cases, it may be necessary to make minor changes
to the source code to disambiguate things like imports or overloaded method
invocations. Downward source compatibility is not supported. If source files
use new APIs, they will not be usable with earlier versions.</p>
<p><b>Workspace Compatibility:</b> EODM 1.0 will be upwards
workspace-compatible with EODM 0.9 unless noted. This means that workspaces and
projects created by an Eclipse with EODM 0.9 installed can be successfully
opened by an Eclipse with EODM 1.0 installed. This includes both hidden
metadata, which is localized to a particular workspace, as well as metadata
files found within a workspace project, which may propagate between workspaces
via file copying or team repositories. User interface session state may be
discarded when a workspace is upgraded. Downward workspace compatibility is not
supported. Metadata files created (or overwritten) by the newer version will
generally be unusable with older versions.</p>
<p><b>Non-compliant usage of API's</b>: All non-API methods and classes, and
certainly everything in a package with &quot;internal&quot; in its name, are
considered implementation details which may vary between operating environment
and are subject to change without notice. Client plug-ins that directly <span
class=GramE>depend</span> on anything other than what is specified in the API
are inherently unsupportable and receive no guarantees about compatibility
within a single release much less with an earlier releases. Refer to <i><a
href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How
to Use the Eclipse API</a></i> for information about how to write compliant
plug-ins.</p>
<h3>Compatibility of OCL 1.2 with 1.1</h3>
<p>The OCL 1.2 component of Eclipse MDT will be compatible with OCL 1.1, except
in those areas noted in the <i style='mso-bidi-font-style:normal'>OCL 1.2
Migration Guide</i>.</p>
<p><b>API Contract Compatibility:</b> OCL 1.2 will be upwards
contract-compatible with OCL 1.1 except in those areas noted in the <i>OCL 1.2
Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>. Programs that
use affected APIs and extension points will need to be ported to OCL 1.2 APIs. Downward
contract compatibility is not supported. There is no guarantee that compliance
with OCL 1.2 APIs would ensure compliance with OCL 1.1 APIs. Refer to <i><a
href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving
Java-based APIs</a></i> for a discussion of the kinds of API changes that
maintain contract compatibility.</p>
<p><b>Binary (plug-in) Compatibility:</b> OCL 1.2 will be upwards
binary-compatible with OCL 1.1 except in those areas noted in the <i>OCL 1.2
Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>. Downward plug-in
compatibility is not supported: plug-ins compiled against OCL 1.2 will likely
be unusable with OCL 1.1. Refer to <i><a
href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving
Java-based APIs</a></i> for a discussion of the kinds of API changes that maintain
binary compatibility.</p>
<p><b>Source Compatibility:</b> Source files written to use OCL 1.1 APIs will
usually compile and run successfully against OCL 1.2 APIs, although this cannot
be guaranteed. In some cases, it may be necessary to make minor changes to the
source code to disambiguate things like imports or overloaded method
invocations. Downward source compatibility is not supported. If source files
use new APIs, they will not be usable with earlier versions.</p>
<p><b>Workspace Compatibility:</b> OCL 1.2 will be upwards workspace-compatible
with OCL 1.1 unless noted. This means that workspaces and projects created by
an Eclipse with OCL 1.1 installed can be successfully opened by an Eclipse with
OCL 1.2 installed. This includes both hidden metadata, which is localized to a
particular workspace, as well as metadata files found within a workspace
project, which may propagate between workspaces via file copying or team
repositories. User interface session state may be discarded when a workspace is
upgraded. Downward workspace compatibility is not supported. Metadata files
created (or overwritten) by the newer version will generally be unusable with
older versions.</p>
<p><b>Non-compliant usage of API's</b>: All non-API methods and classes, and
certainly everything in a package with &quot;internal&quot; in its name, are
considered implementation details which may vary between operating environment
and are subject to change without notice. Client plug-ins that directly <span
class=GramE>depend</span> on anything other than what is specified in the API
are inherently unsupportable and receive no guarantees about compatibility
within a single release much less with an earlier releases. Refer to <i><a
href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How
to Use the Eclipse API</a></i> for information about how to write compliant
plug-ins.</p>
<h3>Compatibility of UML2 2.2 with 2.1</h3>
<p>The UML2 2.2 component of Eclipse MDT will be compatible with UML2 2.1,
except in those areas noted in the <i style='mso-bidi-font-style:normal'>UML2
2.2 Migration Guide</i>.</p>
<p><b>API Contract Compatibility:</b> UML2 2.2 will be upwards
contract-compatible with UML2 2.1 except in those areas noted in the <i>UML2
2.2 Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>. Programs
that use affected APIs and extension points will need to be ported to UML2 2.2
APIs. Downward contract compatibility is not supported. There is no guarantee
that compliance with UML2 2.2 APIs would ensure compliance with UML2 2.1 APIs.
Refer to <i><a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving
Java-based APIs</a></i> for a discussion of the kinds of API changes that
maintain contract compatibility.</p>
<p><b>Binary (plug-in) Compatibility:</b> UML2 2.2 will be upwards
binary-compatible with UML2 2.1 except in those areas noted in the <i>UML2 2.2
Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>. Downward plug-in
compatibility is not supported: plug-ins compiled against UML2 2.2 will likely
be unusable with UML2 2.1. Refer to <i><a
href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving
Java-based APIs</a></i> for a discussion of the kinds of API changes that
maintain binary compatibility.</p>
<p><b>Source Compatibility:</b> Source files written to use UML2 2.1 APIs will
usually compile and run successfully against UML2 2.2 APIs, although this
cannot be guaranteed. In some cases, it may be necessary to make minor changes
to the source code to disambiguate things like imports or overloaded method
invocations. Downward source compatibility is not supported. If source files
use new APIs, they will not be usable with earlier versions.</p>
<p><b>Workspace Compatibility:</b> UML2 2.2 will be upwards
workspace-compatible with UML2 2.1 unless noted. This means that workspaces and
projects created by an Eclipse with UML2 2.1 installed can be successfully
opened by an Eclipse with UML2 2.2 installed. This includes both hidden
metadata, which is localized to a particular workspace, as well as metadata
files found within a workspace project, which may propagate between workspaces
via file copying or team repositories. User interface session state may be
discarded when a workspace is upgraded. Downward workspace compatibility is not
supported. Metadata files created (or overwritten) by the newer version will
generally be unusable with older versions.</p>
<p><b>Non-compliant usage of API's</b>: All non-API methods and classes, and certainly
everything in a package with &quot;internal&quot; in its name, are considered
implementation details which may vary between operating environment and are
subject to change without notice. Client plug-ins that directly <span
class=GramE>depend</span> on anything other than what is specified in the API
are inherently unsupportable and receive no guarantees about compatibility
within a single release much less with an earlier releases. Refer to <i><a
href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How
to Use the Eclipse API</a></i> for information about how to write compliant
plug-ins.</p>
<h3>Compatibility of UML2 Tools 0.8 with 0.7</h3>
<p>The UML2 Tools 0.8 component of Eclipse MDT will be compatible with UML2
Tools 0.7, except in those areas noted in the <i style='mso-bidi-font-style:
normal'>UML2 Tools 0.8 Migration Guide</i>.</p>
<p><b>API Contract Compatibility:</b> UML2 Tools 0.8 will be upwards
contract-compatible with UML2 Tools 0.7 except in those areas noted in the <i>UML2
Tools 0.8 Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>.
Programs that use affected APIs and extension points will need to be ported to
UML2 Tools 0.8 APIs. Downward contract compatibility is not supported. There is
no guarantee that compliance with UML2 Tools 0.8 APIs would ensure compliance
with UML2 Tools 0.7 APIs. Refer to <i><a
href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving
Java-based APIs</a></i> for a discussion of the kinds of API changes that
maintain contract compatibility.</p>
<p><b>Binary (plug-in) Compatibility:</b> UML2 Tools 0.8 will be upwards
binary-compatible with UML2 Tools 0.7 except in those areas noted in the <i>UML2
Tools 0.8 Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>.
Downward plug-in compatibility is not supported: plug-ins compiled against UML2
Tools 0.8 will likely be unusable with UML2 Tools 0.7. Refer to <i><a
href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving
Java-based APIs</a></i> for a discussion of the kinds of API changes that
maintain binary compatibility.</p>
<p><b>Source Compatibility:</b> Source files written to use UML2 Tools 0.7 APIs
will usually compile and run successfully against UML2 Tools 0.8 APIs, although
this cannot be guaranteed. In some cases, it may be necessary to make minor
changes to the source code to disambiguate things like imports or overloaded
method invocations. Downward source compatibility is not supported. If source
files use new APIs, they will not be usable with earlier versions.</p>
<p><b>Workspace Compatibility:</b> UML2 Tools 0.8 will be upwards
workspace-compatible with UML2 Tools 0.7 unless noted. This means that
workspaces and projects created by an Eclipse with UML2 Tools 0.7 installed can
be successfully opened by an Eclipse with UML2 Tools 0.8 installed. This
includes both hidden metadata, which is localized to a particular workspace, as
well as metadata files found within a workspace project, which may propagate
between workspaces via file copying or team repositories. User interface
session state may be discarded when a workspace is upgraded. Downward workspace
compatibility is not supported. Metadata files created (or overwritten) by the
newer version will generally be unusable with older versions.</p>
<p><b>Non-compliant usage of API's</b>: All non-API methods and classes, and
certainly everything in a package with &quot;internal&quot; in its name, are
considered implementation details which may vary between operating environment
and are subject to change without notice. Client plug-ins that directly <span
class=GramE>depend</span> on anything other than what is specified in the API
are inherently unsupportable and receive no guarantees about compatibility
within a single release much less with an earlier releases. Refer to <i><a
href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How
to Use the Eclipse API</a></i> for information about how to write compliant
plug-ins.</p>
<h3>Compatibility of XSD 2.4 with 2.3</h3>
<p>The XSD 2.4 component of Eclipse MDT will be compatible with XSD 2.3, except
in those areas noted in the <i style='mso-bidi-font-style:normal'>XSD 2.4
Migration Guide</i>.</p>
<p><b>API Contract Compatibility:</b> XSD 2.4 will be upwards
contract-compatible with XSD 2.3 except in those areas noted in the <i>XSD 2.4
Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>. Programs that
use affected APIs and extension points will need to be ported to XSD 2.4 APIs.
Downward contract compatibility is not supported. There is no guarantee that
compliance with XSD 2.4 APIs would ensure compliance with XSD 2.3 APIs. Refer
to <i><a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving
Java-based APIs</a></i> for a discussion of the kinds of API changes that
maintain contract compatibility.</p>
<p><b>Binary (plug-in) Compatibility:</b> XSD 2.4 will be upwards
binary-compatible with XSD 2.4 except in those areas noted in the <i>XSD 2.4
Migration</i><i style='mso-bidi-font-style:normal'> Guide</i>. Downward plug-in
compatibility is not supported: plug-ins compiled against XSD 2.4 will likely
be unusable with XSD 2.3. Refer to <i><a
href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving
Java-based APIs</a></i> for a discussion of the kinds of API changes that
maintain binary compatibility.</p>
<p><b>Source Compatibility:</b> Source files written to use XSD 2.3 APIs will
usually compile and run successfully against XSD 2.4 APIs, although this cannot
be guaranteed. Because XSD 2.4 may exploit new Java language constructs, there
is an increased chance of source incompatibilities compared to previous XSD
releases. In some cases, it may be necessary to make minor changes to the
source code to disambiguate things like imports or overloaded method
invocations. Downward source compatibility is not supported. If source files
use new APIs, they will not be usable with earlier versions.</p>
<p><b>Workspace Compatibility:</b> XSD 2.4 will be upwards workspace-compatible
with XSD 2.3 unless noted. This means that workspaces and projects created by
an Eclipse with XSD 2.3 installed can be successfully opened by an Eclipse with
XSD 2.4 installed. This includes both hidden metadata, which is localized to a
particular workspace, as well as metadata files found within a workspace
project, which may propagate between workspaces via file copying or team
repositories. User interface session state may be discarded when a workspace is
upgraded. Downward workspace compatibility is not supported. Metadata files created
(or overwritten) by the newer version will generally be unusable with older
versions.</p>
<p><b>Non-compliant usage of API's</b>: All non-API methods and classes, and
certainly everything in a package with &quot;internal&quot; in its name, are
considered implementation details which may vary between operating environment
and are subject to change without notice. Client plug-ins that directly <span
class=GramE>depend</span> on anything other than what is specified in the API
are inherently unsupportable and receive no guarantees about compatibility within
a single release much less with an earlier releases. Refer to <i><a
href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How
to Use the Eclipse API</a></i> for information about how to write compliant
plug-ins.</p>
<h2>Themes</h2>
<p>The changes under consideration for the next release of Eclipse MDT align
with themes identified by the <a
href="http://www.eclipse.org/org/councils/roadmap_v3_0/themes_v3_0.php">Eclipse
Requirements Council</a> and <a
href="http://wiki.eclipse.org/index.php/Modeling_Project_Plan">Modeling project</a>.</p>
<h2><a name="_EODM_component"></a>EODM component</h2>
<p>EODM is an implementation of RDF(S)/OWL <span class=SpellE>metamodels</span>
of the <a href="http://www.omg.org/ontology">Ontology Definition <span
class=SpellE>Metamodel</span> (ODM)</a> using EMF with additional parsing,
inference, model transformation and editing functions. Plan items reflect new
features of the EODM component, or areas where existing features will be
significantly reworked (<span style='mso-bidi-font-style:italic'><img border=0
width=12 height=12 id="_x0000_i1026" src="../../images/ok.gif"> marks completed
work)</span>.</p>
<h4><span style='font-family:Arial'>Committed Items (EODM component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h4><span style='font-family:Arial'>Proposed Items (EODM component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h4><span style='font-family:Arial'>Deferred Items (EODM component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h2><a name="_OCL_component"></a>OCL component</h2>
<p>OCL is an implementation of the OCL OMG standard for EMF-based models. Plan
items reflect new features of the OCL component, or areas where existing
features will be significantly reworked (<span style='mso-bidi-font-style:italic'><img
border=0 width=12 height=12 id="_x0000_i1027" src="../../images/ok.gif"> marks
completed work)</span>.</p>
<h4><span style='font-family:Arial'>Committed Items (OCL component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><img border=0 width=12 height=12 id="_x0000_i1043"
src="../../images/new.gif"><span class=GramE><b style='mso-bidi-font-weight:
normal'>Extending the OCL grammar for QVT.</b></span> <span class=GramE>Grammar/parser
<span class=SpellE>refactorings</span> for improved extensibility, especially
targeting QVT implementations.</span> (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=176110">176110</a>) [Theme:
End-to-End MDSD]<span style='mso-bidi-font-style:italic'> <img border=0
width=12 height=12 id="_x0000_i1040" src="../../images/ok.gif"></span></p>
<p style='margin-left:27.5pt'><img border=0 width=12 height=12 id="_x0000_i1044"
src="../../images/new.gif"><b style='mso-bidi-font-weight:normal'>Navigation of
unnamed association ends<span style='mso-bidi-font-weight:bold'>.</span></b>
Navigation of unnamed association ends (for UML models) (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=194245">194245</a>) [Theme:
End-to-End MDSD]<span style='mso-bidi-font-style:italic'> <img border=0
width=12 height=12 id="_x0000_i1041" src="../../images/ok.gif"></span></p>
<p style='margin-left:27.5pt'><img border=0 width=12 height=12 id="_x0000_i1045"
src="../../images/new.gif"><span class=SpellE><span class=GramE><b
style='mso-bidi-font-weight:normal'>Customising</b></span></span><span
class=GramE><b style='mso-bidi-font-weight:normal'> error handling<span
style='mso-bidi-font-weight:bold'>.</span></b></span> Redesign of parse error
detection for better error reporting. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=176110">176110</a>) [Theme:
Improved Usability]<span style='mso-bidi-font-style:italic'> <img border=0
width=12 height=12 id="_x0000_i1042" src="../../images/ok.gif"></span></p>
<h4><span style='font-family:Arial'>Proposed Items (OCL component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h4><span style='font-family:Arial'>Deferred Items (OCL component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h2><a name="_OCL_Tools_component"></a>OCL Tools component</h2>
<p>OCL Tools is a set of tools for editing, <span class=SpellE>refactoring</span>,
code generation, execution, and interactive debugging of OCL constraints. Plan
items reflect new features of the OCL Tools component (<span style='mso-bidi-font-style:
italic'><img border=0 width=12 height=12 id="_x0000_i1028"
src="../../images/ok.gif"> marks completed work)</span>.</p>
<h4><span style='font-family:Arial'>Committed Items (OCL Tools component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h4><span style='font-family:Arial'>Proposed Items (OCL Tools component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h4><span style='font-family:Arial'>Deferred Items (OCL Tools component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h2><a name="_UML2_component"></a>UML2 component</h2>
<p>UML2 is an EMF-based implementation of the <a href="http://www.omg.org/uml">UML<sup><span
style='font-size:9.5pt'>TM</span></sup> 2.x <span class=SpellE>metamodel</span></a>
for the Eclipse platform. Plan items reflect new features of the UML2
component, or areas where existing features will be significantly reworked (<span
style='mso-bidi-font-style:italic'><img border=0 width=12 height=12
id="_x0000_i1029" src="../../images/ok.gif"> marks completed work)</span>.</p>
<h4><span style='font-family:Arial'>Committed Items (UML2 component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><img border=0 width=12 height=12 id="_x0000_i1039"
src="../../images/new.gif"><b style='mso-bidi-font-weight:normal'>Profile
Support for <span class=SpellE>Ecore</span> Annotations<span style='mso-bidi-font-weight:
bold'>.</span></b> Because there is no general GUI support for specifying <span
class=SpellE>EAnnotations</span> (since they aren't a standard part of UML)
users currently cannot specify the <span class=SpellE>EAnnotations</span>
they'd like to see in the final <span class=SpellE>Ecore</span>, so it would be
very useful if as part of the <span class=SpellE>Ecore</span> profile, they'd
be able to create <span class=SpellE>EAnnotations</span>. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=184249">184249</a>) [Theme:
End-to-End MDSD]<span style='mso-bidi-font-style:italic'> <img border=0
width=12 height=12 id="_x0000_i1038" src="../../images/ok.gif"></span></p>
<p style='margin-left:27.5pt'><b style='mso-bidi-font-weight:normal'>Support
for (de)serialization to/from CMOF<span style='mso-bidi-font-weight:bold'>.</span></b>
Provide a resource implementation that supports loading/saving UML models in
CMOF format in much the same way that EMF supports loading/saving <span
class=SpellE>Ecore</span> models in EMOF format. Such support should be
integrated into the sample UML editor and importer framework (to allow creating
of EMF projects from CMOF models).better diagnostics for unresolved directives.
(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199624">199624</a>)
[Theme: End-to-End MDSD]<span style='mso-bidi-font-style:italic'> <img
border=0 width=12 height=12 id="_x0000_i1030" src="../../images/ok.gif"></span></p>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>Eclipse 3.4 / EMF 2.4 Compatibility<span style='mso-bidi-font-weight:
bold'>.</span></b></span> Maintain release currency concurrent with EMF 2.4
(and Eclipse 3.4). Make changes as required to align with EMF features and bug
fixes. (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=204200">204200</a>)
[Theme: Upgrade Path]</p>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>Enhanced Documentation.</b></span> Provide enhanced user documentation,
tutorials, white papers, demonstrations etc<span class=GramE>..</span> In
particular, provide a programmerÂ’s guide integrated with the help system in
Eclipse, improve the <span class=SpellE>Javadoc</span> by generating constraint
information (redefines, subsets, union, etc.) into feature and operation
headers, and update the documentation for the UML generator task. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=204201">204201</a>) [Theme:
Ease of Use]</p>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>UML 2.1.2 Compliance<span style='mso-bidi-font-weight:bold'>.</span></b></span>
Provide support for interchange (XMI) compliance with UML 2.1.2. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=204202">204202</a>) [Theme:
Technology Trends]</p>
<h4><span style='font-family:Arial'>Proposed Items (UML2 component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=SpellE><b style='mso-bidi-font-weight:
normal'>BiDi</b></span><b style='mso-bidi-font-weight:normal'> Support<span
style='mso-bidi-font-weight:bold'>.</span></b> Provide better support for <span
class=SpellE>BiDi</span> languages. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=160682">160682</a>) [Theme:
<span style='mso-bidi-font-weight:bold'>Internationalization &amp; Localization</span>]</p>
<h4><span style='font-family:Arial'>Deferred Items (UML2 component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h2><a name="_UML2_Tools_component"></a>UML2 Tools component</h2>
<p>UML2 Tools is set of GMF-based editors for viewing and editing UML models.
Plan items reflect new features of the UML2 Tools component (<span
style='mso-bidi-font-style:italic'><img border=0 width=12 height=12
id="_x0000_i1031" src="../../images/ok.gif"> marks completed work)</span>.</p>
<h4><span style='font-family:Arial'>Committed Items (UML2 Tools component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>Composite Structure Diagrams<span style='mso-bidi-font-weight:bold'>.</span></b></span>
Provide a GMF-based editor for UML composite structure diagrams. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199723">199723</a>) [Theme:
End-to-End MDSD]</p>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>Deployment Diagrams<span style='mso-bidi-font-weight:bold'>.</span></b></span>
Provide a GMF-based editor for UML deployment diagrams. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199724">199724</a>) [Theme:
End-to-End MDSD]</p>
<p style='margin-left:27.5pt'><b style='mso-bidi-font-weight:normal'>Use Case
Diagrams<span style='mso-bidi-font-weight:bold'>.</span></b> Provide a GMF-based
editor for UML use case diagrams. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199725">199725</a>) [Theme:
End-to-End MDSD]</p>
<p style='margin-left:27.5pt'><b style='mso-bidi-font-weight:normal'>Object Diagrams<span
style='mso-bidi-font-weight:bold'>.</span></b> Provide a GMF-based editor for
UML object diagrams. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199726">199726</a>) [Theme:
End-to-End MDSD]</p>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>Structure Diagram Synchronization<span style='mso-bidi-font-weight:
bold'>.</span></b></span> For structure diagrams it makes sense to provide
customizable level of synchronization between semantic and notational models;
in particular, instead of auto-synchronized class diagrams (which always show
the complete contents of the semantic model), different levels of
synchronization should be also supported. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199731">199731</a>) [Theme:
Improved Usability]</p>
<p style='margin-left:27.5pt'><b style='mso-bidi-font-weight:normal'>Diagram
Relations<span style='mso-bidi-font-weight:bold'>.</span></b> With extended set
of 8 diagram types (4 implemented in 0.7 and 4 planned for the next release) it
is essential to provide collaboration of the different diagram types in showing
the different set of aspects for the single semantic model. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199735">199735</a>) [Theme:
Improved Usability]</p>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>Basic OCL Integration<span style='mso-bidi-font-weight:bold'>.</span></b></span>
Integrate the features provided by OCL component with UML2Tools diagrams,
allowing to write/validate/etc OCL expressions in terms of given semantic
model, shown in the diagram. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199737">199737</a>) [Theme:
End-to-End MDSD]</p>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>Extended Profile Support<span style='mso-bidi-font-weight:bold'>.</span></b></span>
Diagram features like choosers, <span class=SpellE>inplace</span> editors,
label providers, creation tools, etc., should be at some extent aware of the
constraints implied by profiles applied to the semantic model. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199739">199739</a>) [Theme:
Improved Usability]</p>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>Diagram-Specific Property Sheets<span style='mso-bidi-font-weight:bold'>.</span></b></span>
Provide custom, extensible property sheets that are aware of the UML2 Tools
arrangement of the semantic elements into notational diagrams. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=199740">199740</a>) [Theme:
Improved Usability]</p>
<h4><span style='font-family:Arial'>Proposed Items (UML2 Tools component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h4><span style='font-family:Arial'>Deferred Items (UML2 Tools component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<h2><a name="_XSD_component"></a>XSD component</h2>
<p>XSD is a library that provides an <a
href="http://www.eclipse.org/modeling/mdt/javadoc/?project=xsd&amp;page=org/eclipse/xsd/package-summary.html&amp;anchor=details">API</a>
for manipulating the components of an XML Schema as described by the <a
href="http://www.w3.org/TR/XMLSchema-0">W3C XML Schema</a> specifications, as
well as an API for manipulating the DOM-accessible representation of XML. Plan
items reflect new features of the XSD component, or areas where existing
features will be significantly reworked (<span style='mso-bidi-font-style:italic'><img
border=0 width=12 height=12 id="_x0000_i1032" src="../../images/ok.gif"> marks
completed work)</span>.</p>
<h4><span style='font-family:Arial'>Committed Items (XSD component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>Improved Diagnostics<span style='mso-bidi-font-weight:bold'>.</span></b></span>
Provide better diagnostics for unresolved directives. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=203607">203607</a>) [Theme:
Ease of Use]</p>
<h4><span style='font-family:Arial'>Proposed Items (XSD component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><b style='mso-bidi-font-weight:
normal'>XML Schema 1.1<span style='mso-bidi-font-weight:bold'>.</span></b></span>
Investigate support for XML Schema 1.1. (<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=204125">204125</a>) [Theme:
Technology Trends]</p>
<h4><span style='font-family:Arial'>Deferred Items (XSD component)<o:p></o:p></span></h4>
<p style='margin-left:27.5pt'><span class=GramE><i style='mso-bidi-font-style:
normal'><span style='mso-bidi-font-weight:bold'>None at this time.</span></i></span><i
style='mso-bidi-font-style:normal'><span style='mso-bidi-font-weight:bold'><o:p></o:p></span></i></p>
<p><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>