| 15 |
</tr> |
</tr> |
| 16 |
<tr> |
<tr> |
| 17 |
<td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td> |
<td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td> |
| 18 |
<td> |
<td> <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>, |
|
| 19 |
<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> |
| 20 |
<p><i>Checklist:</i></p> |
<p><i>Checklist:</i></p> |
| 21 |
<ul> |
<ul> |
| 36 |
<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 |
| 37 |
knowledge of new APIs. Note that most teams have updated the bug report |
knowledge of new APIs. Note that most teams have updated the bug report |
| 38 |
with explanations of their usage.</li> |
with explanations of their usage.</li> |
| 39 |
</ul> |
</ul></td> |
| 40 |
</td> |
</tr> |
| 41 |
|
<tr> |
| 42 |
|
<td ALIGN=RIGHT VALIGN=TOP><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td> |
| 43 |
|
<td><p><strong>Current Status</strong></p> |
| 44 |
|
<p><em>July 21, 2003</em></p> |
| 45 |
|
<ul> |
| 46 |
|
<li>We are still awaiting approval from the Open Source Committee as to |
| 47 |
|
whether or not we can include an XML Pull implementation in the SDK |
| 48 |
|
download</li> |
| 49 |
|
<li>Working out licensing issues with the developers of a particular XML |
| 50 |
|
Pull implementation. (inconsistencies between code and web site)</li> |
| 51 |
|
<li>Have asked for the teams in the SDK to indicate where they use XML |
| 52 |
|
in their code. Almost every single Eclipse team has replied that they |
| 53 |
|
use XML somewhere in their code! Still need to review these uses and |
| 54 |
|
plan for migration.</li> |
| 55 |
|
</ul></td> |
| 56 |
</tr> |
</tr> |
| 57 |
<tr> |
<tr> |
| 58 |
<td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td> |
<td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td> |
| 59 |
<td><p><strong>Milestone Plan (3.0 M2) - July 18, 2003</strong></p> |
<td><p><strong>Milestone Plans</strong></> |
| 60 |
|
<p><em>3.0 M2 - July 18, 2003</em></p> |
| 61 |
<ul> |
<ul> |
| 62 |
<li>Goal is to complete all of the above work.</li> |
<li>Goal is to complete all of the above work.</li> |
| 63 |
<li>We don't envision having all teams converted to new APIs but should |
<li>We don't envision having all teams converted to new APIs but should |
| 69 |
be a part of the Rich Client Platform (RCP) perform this transformation. |
be a part of the Rich Client Platform (RCP) perform this transformation. |
| 70 |
Reducing the size of the XML plug-in shipped with the RCP (3M for Xerces |
Reducing the size of the XML plug-in shipped with the RCP (3M for Xerces |
| 71 |
vs 25K for XmlPull) is a big big win.</li> |
vs 25K for XmlPull) is a big big win.</li> |
| 72 |
|
</ul> |
| 73 |
|
<p><em>3.0 M3 - August 29, 2003</em></p> |
| 74 |
|
<ul> |
| 75 |
|
<li>Continue towards completing the above outlined tasks.</li> |
| 76 |
|
<li>Hope to have approval for XML Pull use shortly after 3.0 M2 and then |
| 77 |
|
will be able to release new code into HEAD.</li> |
| 78 |
</ul></td> |
</ul></td> |
| 79 |
</tr> |
</tr> |
| 80 |
</table> |
</table> |