platform-core-home/plan_xerces.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.8 - (view) (download) (as text)

1 : dj 1.1 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
2 :     <html>
3 :     <head>
4 :     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5 :     <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
6 :     <title>Platform/Core Component Planning Details</title>
7 :     <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
8 :     </head>
9 :     <body text="#000000" bgcolor="#FFFFFF">
10 :     &nbsp;
11 :     <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
12 :     <tr>
13 :     <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF">Platform/Core
14 :     Component Planning Details</font></font></b></td>
15 :     </tr>
16 :     <tr>
17 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
18 : dj 1.4 <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>,
19 : dj 1.1 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=36112">36112</a>)</p>
20 :     <p><i>Checklist:</i></p>
21 : dj 1.3 <ul>
22 : dj 1.1 <li>Create new XML plug-in containing the XML Pull APIs.</li>
23 :     <li>Remove plug-in dependancies from org.eclipse.core.runtime and org.eclipse.core.resources.</li>
24 :     <li>Add new dependancy to new XML plug-in.</li>
25 :     <li>Replace org.eclipse.core.internal.plugins.PluginParser with a new
26 :     parser using the new APIs.</li>
27 :     <li>Replace org.eclipse.core.internal.resources.WorkspaceDescriptionReader
28 :     with new reader based on new APIs.</li>
29 : dj 1.3 <li>Replace org.eclipse.core.internal.resources.ProjectDescriptionReader
30 :     with new reader based on new APIs.</li>
31 : dj 1.4 <li>Determine interaction with bootstrap process. Things to consider include
32 :     creating the bootstrap classloader, update/install, and org.eclipes.core.internal.boot.PlatformConfiguration.</li>
33 : dj 1.1 <li>Check test suites.</li>
34 :     <li>Verify new work by completely removing the Xerces plug-in from the
35 : dj 1.3 environment. (is this possible with the other plug-ins' dependancies?</li>
36 : dj 1.1 <li>Educate Platform/UI and other teams in SDK who rely on Xerces with
37 : dj 1.3 knowledge of new APIs. Note that most teams have updated the bug report
38 :     with explanations of their usage.</li>
39 : dj 1.4 </ul></td>
40 : dj 1.1 </tr>
41 : dj 1.3 <tr>
42 : dj 1.4 <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 : dj 1.6 <p><em>October 20, 2003</em></p>
45 :     <ul>
46 :     <li>Since Eclipse now requires a 1.4 VM, we have decided to program against
47 :     the JAXP APIs for now rather than including a new XML Parser (like XML
48 :     Pull) in the SDK.</li>
49 :     <li>Perhaps in the future we will switch to a highly performant parser
50 :     in the Core Runtime to parse plugin.xml files.</li>
51 :     <li><a href="http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg04227.html">Message</a>
52 :     sent to mailing list and newsgroup.</li>
53 :     <li>Core has removed their dependancy on Xerces and programmed against
54 :     JAXP.</li>
55 :     <li>Other plug-ins in the SDK are following suit.</li>
56 : dj 1.8 </ul> <p><em>September 2, 2003</em></p>
57 :     <ul>
58 :     <li>Still waiting for approval before moving on.</li>
59 :     </ul>
60 :     <p><em>July 21, 2003</em></p>
61 :     <ul>
62 :     <li>We are awaiting to see if we can get approval to include an XML Pull
63 :     implementation in the SDK download</li>
64 :     <li>Working out licensing issues with the developers of a particular XML
65 :     Pull implementation. (inconsistencies between code and web site)</li>
66 :     <li>Have asked for the teams in the SDK to indicate where they use XML
67 :     in their code. Almost every single Eclipse team has replied that they
68 :     use XML somewhere in their code! Still need to review these uses and
69 :     plan for migration.</li>
70 :     </ul>
71 :     </td>
72 : dj 1.4 </tr>
73 :     <tr>
74 : dj 1.3 <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
75 : dj 1.7 <td><p><strong>Milestone Plans</strong>
76 : dj 1.8 <p><em>3.0 M5 - November 21, 2003</em></p>
77 :     <ul>
78 :     <li>Remove dependancy on Xerces for all SDK plug-ins.</li>
79 :     <li>Remove Xerces plug-in from SDK download? Need approval from PMC before
80 :     this can happen.</li>
81 :     </ul> <p><em>3.0 M4 - October 10, 2003</em></p>
82 :     <ul>
83 :     <li>Get the code released into the repository. Still waiting on approval
84 :     before this can be done.</li>
85 :     </ul>
86 :     <p><em>3.0 M3 - August 29, 2003</em></p>
87 :     <ul>
88 :     <li>Continue towards completing the above outlined tasks.</li>
89 :     <li>Hope to have approval for XML Pull use shortly after 3.0 M2 and then
90 :     will be able to release new code into HEAD.</li>
91 :     </ul>
92 : dj 1.5 <p><em>3.0 M2 - July 18, 2003</em></p>
93 : dj 1.3 <ul>
94 :     <li>Goal is to complete all of the above work.</li>
95 :     <li>We don't envision having all teams converted to new APIs but should
96 :     at least be educated on how to convert their code. It is up to the individual
97 :     teams to 1) determine whether or not they want to convert their code
98 :     and 2) to actually change their code.</li>
99 :     <li>Note that although all plug-ins in the SDK are not required to convert
100 :     their parsing, it is necessary that at least the plug-ins defined to
101 :     be a part of the Rich Client Platform (RCP) perform this transformation.
102 :     Reducing the size of the XML plug-in shipped with the RCP (3M for Xerces
103 :     vs 25K for XmlPull) is a big big win.</li>
104 : dj 1.4 </ul>
105 : dj 1.8 </td>
106 : dj 1.3 </tr>
107 : dj 1.1 </table>
108 :    
109 :     </body>
110 :     </html>