| 19 |
<p><b><a name="xerces"></a>Remove Dependancy on Xerces </b>(bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37696">37696</a>, |
<p><b><a name="xerces"></a>Remove Dependancy on Xerces </b>(bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37696">37696</a>, |
| 20 |
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=36112">36112</a>)</p> |
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=36112">36112</a>)</p> |
| 21 |
<p><i>Checklist:</i></p> |
<p><i>Checklist:</i></p> |
| 22 |
<ul type="circle"> |
<ul> |
| 23 |
<li>Create new XML plug-in containing the XML Pull APIs.</li> |
<li>Create new XML plug-in containing the XML Pull APIs.</li> |
| 24 |
<li>Remove plug-in dependancies from org.eclipse.core.runtime and org.eclipse.core.resources.</li> |
<li>Remove plug-in dependancies from org.eclipse.core.runtime and org.eclipse.core.resources.</li> |
| 25 |
<li>Add new dependancy to new XML plug-in.</li> |
<li>Add new dependancy to new XML plug-in.</li> |
| 27 |
parser using the new APIs.</li> |
parser using the new APIs.</li> |
| 28 |
<li>Replace org.eclipse.core.internal.resources.WorkspaceDescriptionReader |
<li>Replace org.eclipse.core.internal.resources.WorkspaceDescriptionReader |
| 29 |
with new reader based on new APIs.</li> |
with new reader based on new APIs.</li> |
| 30 |
|
<li>Replace org.eclipse.core.internal.resources.ProjectDescriptionReader |
| 31 |
|
with new reader based on new APIs.</li> |
| 32 |
|
<li>Determine interaction with bootstrap process. Things to consider include |
| 33 |
|
creating the bootstrap classloader, update/install, and org.eclipes.core.internal.boot.PlatformConfiguration.</li> |
| 34 |
<li>Check test suites.</li> |
<li>Check test suites.</li> |
| 35 |
<li>Verify new work by completely removing the Xerces plug-in from the |
<li>Verify new work by completely removing the Xerces plug-in from the |
| 36 |
environment.</li> |
environment. (is this possible with the other plug-ins' dependancies?</li> |
| 37 |
<li>Educate Platform/UI and other teams in SDK who rely on Xerces with |
<li>Educate Platform/UI and other teams in SDK who rely on Xerces with |
| 38 |
knowledge of new APIs.</li> |
knowledge of new APIs. Note that most teams have updated the bug report |
| 39 |
|
with explanations of their usage.</li> |
| 40 |
</ul> |
</ul> |
| 41 |
</td> |
</td> |
| 42 |
</tr> |
</tr> |
| 43 |
<tr> </tr> |
<tr> |
| 44 |
|
<td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td> |
| 45 |
|
<td><p><strong>Milestone Plan (3.0 M2) - July 18, 2003</strong></p> |
| 46 |
|
<ul> |
| 47 |
|
<li>Goal is to complete all of the above work.</li> |
| 48 |
|
<li>We don't envision having all teams converted to new APIs but should |
| 49 |
|
at least be educated on how to convert their code. It is up to the individual |
| 50 |
|
teams to 1) determine whether or not they want to convert their code |
| 51 |
|
and 2) to actually change their code.</li> |
| 52 |
|
<li>Note that although all plug-ins in the SDK are not required to convert |
| 53 |
|
their parsing, it is necessary that at least the plug-ins defined to |
| 54 |
|
be a part of the Rich Client Platform (RCP) perform this transformation. |
| 55 |
|
Reducing the size of the XML plug-in shipped with the RCP (3M for Xerces |
| 56 |
|
vs 25K for XmlPull) is a big big win.</li> |
| 57 |
|
</ul></td> |
| 58 |
|
</tr> |
| 59 |
</table> |
</table> |
| 60 |
|
|
| 61 |
</body> |
</body> |