|
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 <title>Eclipse Project Release Notes 3.5</title> |
|
6 </head> |
|
7 <body> |
|
8 |
|
9 <h1>Eclipse Project Release Notes</h1> |
|
10 <p>Release 3.5.0<br> |
|
11 Last revised June 11, 2009</p> |
|
12 <p align="left"><strong>This software is OSI Certified Open Source Software.<br> |
|
13 OSI Certified is a certification mark of the Open Source Initiative. </strong></p> |
|
14 <blockquote> |
|
15 <p align="left"><a href="#TargetOperatingEnvironments">1. Target Operating |
|
16 Environments</a><br> |
|
17 <a href="#Compatibility">2. Compatibility with Previous |
|
18 Releases</a><br> |
|
19 <a href="#Known Issues">3. Known Issues</a><br> |
|
20 <a href="#Running Eclipse">4. Running Eclipse</a><br> |
|
21 <a href="#Upgrading">5. Upgrading a Workspace from a Previous Release</a><br> |
|
22 <a href="#Interoperability with Previous Releases">6. Interoperability with |
|
23 Previous Releases</a><br> |
|
24 </p> |
|
25 </blockquote> |
|
26 |
|
27 <h2>1. <a name="TargetOperatingEnvironments"></a>Target Operating Environments</h2> |
|
28 <p>In order to remain current, each Eclipse Project release targets reasonably current |
|
29 operating environments.</p> |
|
30 <p>Most of the Eclipse SDK is "pure" Java code and has no direct dependence |
|
31 on the underlying operating system. The chief dependence is therefore on the |
|
32 Java Platform itself. Portions are targeted to specific classes of operating |
|
33 environments, requiring their source code to only reference facilities available |
|
34 in particular class libraries (e.g. J2ME Foundation 1.0, J2SE 1.3 and 1.4, |
|
35 etc.).</p> |
|
36 |
|
37 <p>In general, the 3.5 release of the Eclipse Project is developed on a mix |
|
38 of Java 1.4, Java 5 and Java 6 VMs. As such, the Eclipse SDK as a whole |
|
39 is targeted at all modern, desktop Java VMs. Full functionality is available for |
|
40 1.4 level development everywhere, and extended development capabilities are made |
|
41 available on the VMs that support them.</p> |
|
42 <p><a href="#Appendix1">Appendix 1</a> contains a table that indicates the class |
|
43 library level required for each bundle.</p> |
|
44 <p>There are many different implementations of the Java Platform running atop |
|
45 a variety of operating systems. We focus our testing on a handful of |
|
46 popular combinations of operating system and Java Platform; these are our <em>reference |
|
47 platforms</em>. Eclipse undoubtedly runs fine in many operating environments |
|
48 beyond the reference platforms we test. However, since we do not systematically test |
|
49 them we cannot vouch for them. Problems encountered when running Eclipse on a |
|
50 non-reference platform that cannot be recreated on any reference platform will |
|
51 be given lower priority than problems with running Eclipse on a reference platform.</p> |
|
52 <p>Eclipse 3.5 is tested and validated on the following reference platforms</p> |
|
53 |
|
54 |
|
55 <table border="1" cellpadding="2" cellspacing="2" width="80%" summary="Eclipse Reference Platforms"> |
|
56 <tbody> |
|
57 <tr align="center"> |
|
58 <td><b>Reference Platforms</b></td> |
|
59 </tr> |
|
60 <tr> |
|
61 <td><b>Microsoft Windows Vista, x86-32, Win32</b> running (any of): |
|
62 <ul> |
|
63 <li>Sun Java Standard Edition 5 Update 14 for Microsoft Windows</li> |
|
64 <li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li> |
|
65 <li>BEA JRockit 27.4.0, for Microsoft Windows</li> |
|
66 </ul></td> |
|
67 </tr> |
|
68 <tr> |
|
69 <td><b>Microsoft Windows XP, x86-32, Win32</b> running (any of): |
|
70 <ul> |
|
71 <li>Sun Java Standard Edition 6 Update 3 for Microsoft Windows</li> |
|
72 <li>Sun Java Standard Edition 5 Update 14 for Microsoft Windows</li> |
|
73 <li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li> |
|
74 <li>BEA JRockit 27.4.0, for Microsoft Windows</li> |
|
75 <li>Sun Java Standard Edition 1.4.2_16 for Microsoft Windows</li> |
|
76 <li>IBM 32-bit SDK for Windows, Java 2 Technology Edition 1.4.2 SR10</li> |
|
77 </ul></td> |
|
78 </tr> |
|
79 <tr> |
|
80 <td><b>Red Hat Enterprise Linux 5.0, x86-32, GTK</b> running (any of): |
|
81 <ul> |
|
82 <li> Sun Java Standard Edition 6 Update 3 for Linux x86</li> |
|
83 <li>Sun Java Standard Edition 5 Update 14 for Linux x86</li> |
|
84 <li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b</li> |
|
85 <li>BEA JRockit 27.4.0, for Linux x86</li> |
|
86 <li>Sun Java Standard Edition 1.4.2_16 for Linux x86</li> |
|
87 <li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 1.4.2 SR10</li> |
|
88 </ul></td> |
|
89 </tr> |
|
90 <tr> |
|
91 <td><b>SUSE Linux Enterprise Server 10, x86-32, GTK</b> running (any of): |
|
92 <ul> |
|
93 <li>Sun Java Standard Edition 5 Update 14 for Linux x86</li> |
|
94 <li>IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b</li> |
|
95 </ul></td> |
|
96 </tr> |
|
97 <tr> |
|
98 <td><b>SUSE Linux Enterprise Server 10, x86-64, GTK</b> running (any of): |
|
99 <ul> |
|
100 <li>Sun Java Standard Edition 5 Update 14 for Linux x86-64</li> |
|
101 <li>IBM 64-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b</li> |
|
102 </ul></td> |
|
103 </tr> |
|
104 <tr> |
|
105 <td><b>Microsoft Windows Vista, x86-64, Win32</b> running (any of): |
|
106 <ul> |
|
107 <li>Sun Java Standard Edition 5 Update 14 for Microsoft Windows (AMD64/EM64T)</li> |
|
108 <li>IBM 64-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li> |
|
109 </ul></td> |
|
110 </tr> |
|
111 <tr> |
|
112 <td><b>Microsoft Windows XP Professional x64 Edition, x86-64, Win32</b> running (any of): |
|
113 <ul> |
|
114 <li>Sun Java Standard Edition 5 Update 14 for Microsoft Windows (AMD64/EM64T)</li> |
|
115 <li>IBM 64-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b</li> |
|
116 </ul></td> |
|
117 </tr> |
|
118 <tr> |
|
119 <td><b>Red Hat Enterprise Linux 4.0 update 2, x86-64, GTK</b> running: |
|
120 <ul> |
|
121 <li>Sun Java Standard Edition 5 Update 14 for Linux x86-64</li> |
|
122 <li>IBM 64-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b</li> |
|
123 </ul></td> |
|
124 </tr> |
|
125 <tr> |
|
126 <td><b>Sun Solaris 10, SPARC, GTK</b> running: |
|
127 <ul> |
|
128 <li>Sun Java Standard Edition 5 Update 14 for Solaris SPARC</li> |
|
129 </ul></td> |
|
130 </tr> |
|
131 <tr> |
|
132 <td><b>Sun Solaris 10, x86, GTK</b> running: |
|
133 <ul> |
|
134 <li>Sun Java Standard Edition 5 Update 14 for Solaris</li> |
|
135 </ul></td> |
|
136 </tr> |
|
137 <tr> |
|
138 <td><b>HP-UX 11i v2, ia64, Motif 2.1, GTK</b> running: |
|
139 <ul> |
|
140 <li>HP-UX Java Standard Edition 5 Update 7 for Itanium</li> |
|
141 </ul></td> |
|
142 </tr> |
|
143 <tr> |
|
144 <td><b>IBM AIX 5.3, Power, Motif 2.1</b> running: |
|
145 <ul> |
|
146 <li>IBM 32-bit SDK, Java 2 Technology Edition 5.0, SR6b</li> |
|
147 </ul></td> |
|
148 </tr> |
|
149 <tr> |
|
150 <td><b>Red Hat Enterprise Linux 5.0, Power, GTK</b> running: |
|
151 <ul> |
|
152 <li>IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 5.0, SR6b</li> |
|
153 </ul></td> |
|
154 </tr> |
|
155 <tr> |
|
156 <td><b>SUSE Linux Enterprise Server 10, Power, GTK</b> running: |
|
157 <ul> |
|
158 <li>IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 5.0, SR6b</li> |
|
159 </ul></td> |
|
160 </tr> |
|
161 <tr> |
|
162 <td><b>Apple Mac OS X 10.5, Universal, Carbon</b> running: |
|
163 <ul> |
|
164 <li>Apple Java for Mac OS X 10.5, Update 1</li> |
|
165 </ul></td> |
|
166 </tr> |
|
167 <tr> |
|
168 <td><b>Apple Mac OS X 10.5, Universal 32-bit, Cocoa</b> running: |
|
169 <ul> |
|
170 <li>Apple Java for Mac OS X 10.5, Update 1</li> |
|
171 </ul></td> |
|
172 </tr> |
|
173 <tr> |
|
174 <td><b>Apple Mac OS X 10.5, Universal 64-bit, Cocoa</b> running: |
|
175 <ul> |
|
176 <li>Apple Java for Mac OS X 10.5, Update 1</li> |
|
177 </ul></td> |
|
178 </tr> |
|
179 </tbody> |
|
180 </table> |
|
181 |
|
182 |
|
183 <p>As stated above, <i>we expect that Eclipse works fine on other current |
|
184 Java VM and OS versions but we cannot flag these as reference platforms without |
|
185 significant community support for testing them.</i></p> |
|
186 <h4>Internationalization</h4> |
|
187 <p>The Eclipse SDK is designed as the basis for internationalized products. The |
|
188 user interface elements provided by the Eclipse SDK components, including dialogs |
|
189 and error messages, are externalized. The English strings are provided as the |
|
190 default resource bundles.</p> |
|
191 |
|
192 <p>Latin-1 and DBCS locales are supported by the Eclipse SDK on all reference platforms; |
|
193 BIDI locales are supported by the Eclipse SDK everywhere but on Motif.</p> |
|
194 <p>The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard, |
|
195 on Windows XP and 2000, Linux/GTK and the Macintosh.</p> |
|
196 <p>German and Japanese locales are tested.</p> |
|
197 |
|
198 <h2>2. <a name="Compatibility"></a>Compatibility with Previous Releases</h2> |
|
199 <h3>Compatibility of Release 3.5 with 3.4</h3> |
|
200 <p>Eclipse 3.5 is compatible with Eclipse 3.4 (and all earlier 3.x versions).</p> |
|
201 |
|
202 <p><strong>API Contract Compatibility:</strong> Eclipse SDK 3.5 is upwards |
|
203 contract-compatible with Eclipse SDK 3.4 except in those areas noted in the |
|
204 <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_5_porting_guide.html" target="_top"> |
|
205 <em>Eclipse 3.5 Plug-in Migration Guide</em> |
|
206 </a>. Programs that use affected APIs and extension points will need to be ported |
|
207 to Eclipse SDK 3.5 APIs. Downward contract compatibility |
|
208 is not supported. There is no guarantee that compliance with Eclipse SDK 3.5 |
|
209 APIs would ensure compliance with Eclipse SDK 3.4 APIs. Refer to |
|
210 <a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs"> |
|
211 <em>Evolving Java-based APIs</em> |
|
212 </a> for a discussion of the kinds of API changes that maintain contract compatibility.</p> |
|
213 |
|
214 <p><strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 3.5 is upwards |
|
215 binary-compatible with Eclipse SDK 3.4 except in those areas noted in the |
|
216 <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_5_porting_guide.html" target="_top"> |
|
217 <em>Eclipse 3.5 Plug-in Migration Guide</em> |
|
218 </a>. Downward plug-in compatibility is not supported. Plug-ins developed for Eclipse SDK |
|
219 3.5 will not be usable in Eclipse SDK 3.4. Refer to |
|
220 <a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs"> |
|
221 <em>Evolving Java-based APIs</em> |
|
222 </a> for a discussion of the kinds of API changes that maintain binary compatibility.</p> |
|
223 |
|
224 <p><strong>Source Compatibility:</strong> Eclipse SDK 3.5 is upwards source-compatible |
|
225 with Eclipse SDK 3.4 except in the areas noted in the |
|
226 <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.platform.doc.isv/porting/eclipse_3_5_porting_guide.html" target="_top"> |
|
227 |
|
228 <em>Eclipse 3.5 Plug-in Migration Guide</em> |
|
229 </a>. This means that source files written |
|
230 to use Eclipse SDK 3.4 APIs might successfully compile and run against Eclipse |
|
231 SDK 3.5 APIs, although this is not guaranteed. Downward source compatibility |
|
232 is not supported. If source files use new Eclipse SDK APIs, they will not be |
|
233 usable with an earlier version of the Eclipse SDK. </p> |
|
234 |
|
235 <p><strong>Workspace Compatibility:</strong> Eclipse SDK 3.5 is upwards |
|
236 workspace-compatible with earlier 3.x versions of the Eclipse SDK unless noted. |
|
237 This means that workspaces and projects created with Eclipse SDK 3.0 to 3.4 can be successfully |
|
238 opened by Eclipse SDK 3.5 and upgraded to a 3.5 workspace. This includes both |
|
239 hidden metadata, which is localized to a particular workspace, as well as metadata |
|
240 files found within a workspace project (e.g., the .project file), which may |
|
241 propagate between workspaces via file copying or team repositories. Individual |
|
242 plug-ins developed for Eclipse SDK 3.5 should provide similar upwards compatibility |
|
243 for their hidden and visible workspace metadata created by earlier versions; |
|
244 3.5 plug-in developers are responsible for ensuring that their plug-ins recognize |
|
245 metadata from earlier versions and process it appropriately. User |
|
246 interface session state may be discarded when a workspace is upgraded. Downward |
|
247 workspace compatibility is not supported. A workspace created (or opened) by |
|
248 a product based on Eclipse 3.5 will be unusable with a product based on an earlier |
|
249 version of Eclipse. Visible metadata files created (or overwritten) by Eclipse |
|
250 3.5 will generally be unusable with earlier versions of Eclipse. </p> |
|
251 |
|
252 <p><strong>Non-compliant usage of API's</strong>: All non-API methods and classes, |
|
253 and certainly everything in a package with "internal" in its name, |
|
254 are considered implementation details which may vary between operating environment |
|
255 and are subject to change without notice. Client plug-ins that directly depend |
|
256 on anything other than what is specified in the Eclipse SDK API are inherently |
|
257 unsupportable and receive no guarantees about compatibility within a single |
|
258 release much less with earlier releases. Refer to |
|
259 <a href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html"> |
|
260 <em>How to Use the Eclipse API</em></a> |
|
261 for information about how to write compliant plug-ins. </p> |
|
262 |
|
263 <h2>3. <a name="Known Issues"></a> Known Issues</h2> |
|
264 <blockquote> |
|
265 <a href="#I-General"> |
|
266 3.1 General problems</a><br> |
|
267 <a href="#I-General-Startup">3.1.1 Startup</a><br> |
|
268 <a href="#I-General-GCJ">3.1.2 GCJ</a><br> |
|
269 <a href="#I-General-64bitJava">3.1.3 64-bit Java HotSpot(TM) VM</a><br> |
|
270 <a href="#I-Platform">3.2 Platform</a><br> |
|
271 <a href="#I-Platform-Core">3.2.1 Core</a><br> |
|
272 |
|
273 <a href="#I-Platform-Ant">3.2.2 Ant</a><br> |
|
274 <a href="#I-Platform-User-Assistance">3.2.3 User Assistance</a><br> |
|
275 <a href="#I-Platform-UI">3.2.4 UI</a><br> |
|
276 <a href="#I-Platform-Text">3.2.5 Text</a><br> |
|
277 <a href="#I-Platform-SWT">3.2.6 SWT</a><br> |
|
278 |
|
279 <a href="#I-Platform-Team-CVS">3.2.7 Team and CVS</a><br> |
|
280 <a href="#I-Platform-Install-Update">3.2.8 Install/Update</a><br> |
|
281 <a href="#I-Platform-Debug">3.2.9 Debug</a><br> |
|
282 <a href="#I-Platform-Compare">3.2.10 Compare</a><br> |
|
283 <a href="#I-JDT"> |
|
284 3.3 Java development tools (JDT)</a><br> |
|
285 <a href="#I-PDE"> |
|
286 3.4 Plug-in Development Environment (PDE)</a><br> |
|
287 |
|
288 </blockquote> |
|
289 <p>Note: Bug numbers refer to the Eclipse project bug database at <a href="http://dev.eclipse.org/bugs/">http://bugs.eclipse.org/bugs/</a></p> |
|
290 |
|
291 <h3>3.1 <a name="I-General">General problems</a></h3> |
|
292 <h3>3.1.1 <a name="I-General-Startup">General - Startup</a></h3> |
|
293 <h4>Installation/Configuration issues that can cause Eclipse to fail start</h4> |
|
294 <p>Here are some common problems that can cause Eclipse not to start:</p> |
|
295 <ul> |
|
296 <li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 3.5 requires |
|
297 at least a 1.4.2 VM. Perhaps an older version of the VM is being found in |
|
298 your path. To explicitly specify which VM to run with, use the Eclipse <tt>-vm</tt> |
|
299 command-line argument. (See also the <a href="#Running Eclipse">Running Eclipse</a> |
|
300 section below.)</li> |
|
301 <li> |
|
302 Running Eclipse on Gentoo Linux may result in the following error message: |
|
303 <div style="margin-left: 40px;"> |
|
304 <tt>* run-java-tool is not available for sun-jdk-1.6 on i686<br>* IMPORTANT: some Java tools are not available on some VMs on some architectures</tt> |
|
305 </div> |
|
306 |
|
307 If this occurs, start Eclipse by specifying a -vm argument, either |
|
308 specify the path to a java vm or use: <tt>eclipse -vm `java-config</tt> |
|
309 --java` (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=176021">176021</a>)</li> |
|
310 <li>Eclipse must be installed to a clean directory and not installed over top of |
|
311 a previous installation. If you have done this then please re-install to a new |
|
312 directory. If your workspace is in a child directory of your old installation |
|
313 directory, then see the instructions below on "<a href="#upgrading">Upgrading Workspace from a |
|
314 Previous Release"</a>.</li> |
|
315 |
|
316 <li>Java sometimes has difficulty detecting whether a file system is writable. In |
|
317 particular, the method java.io.File.canWrite() appears to return true in |
|
318 unexpected cases (e.g., using Windows drive sharing where the share is a |
|
319 read-only Samba drive). The Eclipse runtime generally needs a writable |
|
320 configuration area and as a result of this problem, may erroneously detect the |
|
321 current configuration location as writable. The net result is that Eclipse will |
|
322 fail to start and depending on the circumstances, may fail to write a log file |
|
323 with any details. To work around this, we suggest users experiencing this |
|
324 problem set their configuration area explicitly using the <tt>-configuration</tt> command |
|
325 line argument. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=67719">67719</a>)</li> |
|
326 </ul> |
|
327 |
|
328 <h4><b>Invalid characters in install directory prevents Eclipse from starting</b></h4> |
|
329 <p>Eclipse will fail to launch if installed in a directory whose path |
|
330 contains certain invalid characters, including :%#<>"!. The |
|
331 workaround is to install Eclipse in a directory whose path does not contain |
|
332 invalid characters. (bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=3109">3109</a> |
|
333 and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=17281">17281</a>)</p> |
|
334 |
|
335 <h4>Hanging during class loading when out of permanent generation memory</h4> |
|
336 <p> |
|
337 The Sun VM may hang indefinitely during class loading if it runs out of permanent |
|
338 generation memory. This will cause CPU usage to stay at 100% until the process |
|
339 is ended. See the section <a href="#Running Eclipse">Running Eclipse</a> for details |
|
340 on addressing this VM problem. |
|
341 </p> |
|
342 |
|
343 <h3>3.1.2 <a name="I-General-GCJ">General - GCJ</a></h3> |
|
344 <p>GCJ is an effort by the GCC team to provide an open source Java compiler and |
|
345 runtime environment to interpret Java bytecode. Unfortunately, the GCJ runtime |
|
346 environment is not an environment that is often tested on by Eclipse developers.</p> |
|
347 |
|
348 <p>The most common problems surrounding GCJ are:</p> |
|
349 <ul> |
|
350 <li>Eclipse does not start at all</li> |
|
351 <li>Eclipse throws a 'java.lang.ClassNotFoundException: org.eclipse.core.runtime.Plugin' that can be found in the logs (located in |
|
352 workspace/.metadata/.log)</li> |
|
353 </ul> |
|
354 |
|
355 <p>The workspace's log file is a good place to check to identify whether GCJ is |
|
356 being used or not. Every Eclipse log session is prepended with |
|
357 information about the runtime environment that was used to run Eclipse. The log |
|
358 may include something like the following:</p> |
|
359 |
|
360 <code>java.fullversion=GNU libgcj 4.2.1 (Debian 4.2.1-5)</code> |
|
361 |
|
362 <p>If Eclipse does start, one can check which runtime environment is being used to |
|
363 run Eclipse by going to <b>Help > About Eclipse SDK > Installation Details > Configuration</b>. The |
|
364 <b>About</b> dialog itself can also provide other information, the build identifier |
|
365 can be of particular interest as it is tagged by some distributions. This allows the |
|
366 user to identify whether Eclipse was downloaded through the distribution's |
|
367 package management system or directly from the eclipse.org website.</p> |
|
368 |
|
369 Eg: <code>Build id: M20070212-1330 (Ubuntu version: 3.2.2-0ubuntu3)</code> |
|
370 |
|
371 <p>The two most common workarounds are:</p><ul> |
|
372 <li>download the Eclipse binary from eclipse.org directly</li> |
|
373 <li>run Eclipse using an alternate Java runtime environment</li></ul> |
|
374 |
|
375 <p>To download Eclipse, try one of the links below:</p><ul> |
|
376 <li><a href="http://www.eclipse.org/downloads/">http://www.eclipse.org/downloads/</a></li> |
|
377 <li><a href="http://download.eclipse.org/eclipse/downloads/">http://download.eclipse.org/eclipse/downloads/</a></li></ul> |
|
378 |
|
379 It is imperative that 64-bit builds are downloaded and used if a 64-bit Java |
|
380 runtime environment has been installed. Below are two sample tarball names of |
|
381 version 3.5.0 of the Eclipse SDK packaged for 32-bit and 64-bit processors. |
|
382 |
|
383 <pre>eclipse-SDK-3.5-linux-gtk.tar.gz (32-bit) |
|
384 eclipse-SDK-3.5-linux-gtk-x86_64.tar.gz (64-bit)</pre> |
|
385 |
|
386 <p>To run Eclipse with an alternate Java runtime environment, the path to the Java |
|
387 virtual machine's binary must be identified. With an Eclipse installation from |
|
388 the distribution, altering the $PATH variable to include the path to the |
|
389 alternate Java runtime environment is often not enough as the Eclipse that |
|
390 Linux distributions package often performs a scan internally to pick up GCJ by |
|
391 itself whilst ignoring what's on the $PATH. An example of the terminal's output |
|
392 is shown below:</p> |
|
393 |
|
394 <code>searching for compatible vm...<br> |
|
395 testing /usr/lib/jvm/java-7-icedtea...not found<br> |
|
396 testing /usr/lib/jvm/java-gcj...found</code> |
|
397 |
|
398 <p>Once the path to the virtual machine's binary has been identified, try running |
|
399 Eclipse with the following command:</p> |
|
400 |
|
401 <code>./eclipse -vm /path/to/jre/bin/java</code> |
|
402 |
|
403 <p>For an actual example, it might look something like the following:</p> |
|
404 |
|
405 <code>./eclipse -vm /usr/lib/jvm/sun-java-6/bin/java<br> |
|
406 ./eclipse -vm /opt/sun-jdk-1.6.0.02/bin/java</code> |
|
407 |
|
408 <p>If this seems to solve the problem, it is likely that the problem really was |
|
409 related to the use of GCJ as the Java runtime for running Eclipse. The |
|
410 eclipse.ini file located within Eclipse's folder can be altered to |
|
411 automatically pass this argument to Eclipse at startup. An example of its |
|
412 content is presented below:</p> |
|
413 |
|
414 <code>-showsplash<br> |
|
415 org.eclipse.platform<br> |
|
416 --launcher.XXMaxPermSize<br> |
|
417 256m<br> |
|
418 -vm<br> |
|
419 /opt/sun-jdk-1.6.0.02/bin/java<br> |
|
420 -vmargs<br> |
|
421 -Xms40m<br> |
|
422 -Xmx512m</code> |
|
423 |
|
424 <p>Note that every argument must be on its own line. More information about the |
|
425 eclipse.ini file can be found at <a href="http://wiki.eclipse.org/Eclipse.ini">http://wiki.eclipse.org/Eclipse.ini</a>.</p> |
|
426 |
|
427 <p>If problems persists after downloading an installation of Eclipse from |
|
428 eclipse.org and using a supported Java runtime environment (a list of which may be found <a href="#TargetOperatingEnvironments">above</a>), |
|
429 you can seek further assistance through the <a href="http://www.eclipse.org/newsgroups/">newsgroups</a>, |
|
430 the IRC <a href="irc://irc.freenode.net/#eclipse">channel</a>, |
|
431 and/or <a href="https://bugs.eclipse.org/bugs/">bugzilla</a>. |
|
432 </p> |
|
433 |
|
434 <h3>3.1.3 <a name="I-General-64bitJava">General - 64-bit Java HotSpot(TM) VM</a></h3> |
|
435 <p> |
|
436 There is a known issue with the Java HotSpot(TM) 1.6.0 VM compiler which causes eclipse to |
|
437 crash (see Sun bug <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6614100">http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6614100</a>, |
|
438 and Eclipse bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=214092">214092</a>). |
|
439 The crash usually occurs within a VM CompilerThread when attempting to compile the method org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith. |
|
440 </p> |
|
441 <p> |
|
442 This problem has been addressed in Sun Java 6 update 11, so the simplest resolution is |
|
443 to obtain the latest JRE release for your platform. |
|
444 To work around the issue you can exclude the method org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith from being compiled with the following |
|
445 VM argument: |
|
446 </p> |
|
447 |
|
448 <code> |
|
449 -XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith |
|
450 </code> |
|
451 |
|
452 <p> |
|
453 This VM argument can be placed in the eclipse.ini file after the -vmargs line like the following: |
|
454 </p> |
|
455 |
|
456 <code> |
|
457 -startup<br> |
|
458 plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090306-1900<br> |
|
459 --launcher.library<br> |
|
460 plugins/org.eclipse.equinox.launcher_1.0.200.v20090429-1630.jar<br> |
|
461 -showsplash<br> |
|
462 org.eclipse.platform<br> |
|
463 --launcher.XXMaxPermSize<br> |
|
464 256m<br> |
|
465 -vmargs<br> |
|
466 -XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith<br> |
|
467 -Xms40m<br> |
|
468 -Xmx256m<br> |
|
469 </code> |
|
470 |
|
471 <p> |
|
472 There have been reports of other classes that cause the compiler to crash. If all else fails you can |
|
473 disable the compiler with the VM arg "-Xint". |
|
474 </p> |
|
475 |
|
476 <h3>3.2 <a name="I-Platform">Platform</a></h3> |
|
477 |
|
478 <h3>3.2.1 <a name="I-Platform-Core">Platform - Core</a></h3> |
|
479 |
|
480 <h4>Installing plug-ins by unzipping them into the plugins directory</h4> |
|
481 <p>New plug-ins can be installed into the system by unzipping them into the plugins |
|
482 directory. However this is not recommended, and the dropins directory should be |
|
483 used for this purpose instead. Note that unzipping a different |
|
484 version of a plug-in that is already installed will have no effect. To change the version |
|
485 of a plug-in installed in your system, you need to either perform an update, or install |
|
486 a feature patch.</p> |
|
487 |
|
488 <h4>XML files with UTF-8 byte order mark fail to have content type detected</h4> |
|
489 <p>Eclipse will fail to detect the proper content type for XML files that have a |
|
490 UTF-8 byte order mark if Crimson is the XML parser (as it is on Sun 1.4 JREs, |
|
491 but not on Sun 1.5 JREs). This |
|
492 problem will prevent actions normally available when files of the affected |
|
493 content types are selected from being presented to the user. The workaround is |
|
494 to ensure the default XML parser supports UTF-8 BOMs (such as Xerces does). (bug |
|
495 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=67048">67048</a>)</p> |
|
496 <h4>No branding with old config.ini</h4> |
|
497 <p>If you have an old config.ini file and use it with a new Eclipse build, you |
|
498 may not get the correct product branding. This is because the id of the standard |
|
499 Eclipse product changed. Users in shared install scenarios may end up in this |
|
500 situation as previous builds of Eclipse automatically generated config.ini files |
|
501 in some cases. The work around is either to delete the local config.ini or |
|
502 update the eclipse.product line to read eclipse.product=org.eclipse.platform.ide.</p> |
|
503 |
|
504 <h4>Problems with |
|
505 classloaders in created threads</h4> |
|
506 <p>There is a known issue with trying to load classes from a newly-created |
|
507 thread using a class loader different from the plug-in class loader. The result |
|
508 will be a <code>ClassNotFoundException</code>. As a workaround, do the |
|
509 following:</p> |
|
510 <ol> |
|
511 <li>Create a thread in which to run your code.</li> |
|
512 <li>Send yourThread.setContextClassLoader(yourClassLoader); // you can find |
|
513 your classloader by grabbing a class it loaded (YourPluginClass.class.getClassLoader())</li> |
|
514 <li>Run your code in the newly created thread.</li> |
|
515 </ol> |
|
516 <p>If you set the context class loader for the current thread, you are |
|
517 competing with other users of the thread (all of Eclipse), so the results will |
|
518 be unpredictable. However, there should be no problem in practice provided you |
|
519 reset the context class loader back to its original value when your use in the |
|
520 current thread is complete. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=8907">8907</a>)</p> |
|
521 |
|
522 <h4>Deadlock creating executable |
|
523 extension in Plugin.startup</h4> |
|
524 <p>If <code>Plugin.startup</code> code is too complex and performs tasks such |
|
525 as creating an executable extension, a deadlock situation can be created. Only |
|
526 simple bookkeeping tasks should be performed in <code>Plugin.startup</code> |
|
527 code. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=5875">5875</a>)</p> |
|
528 <h4>Potential Problems Converting Plug-in Manifests</h4> |
|
529 <p>If your plug-in ships with a plug-in manifest and not an OSGi bundle manifest, |
|
530 is shipped as a JAR file, and contains a nested JAR file then there may be |
|
531 problems in the automatic generation of the bundle manifest file. The packages |
|
532 defined in the nested JAR may not be exported correctly in the <tt>Export-packages</tt> |
|
533 |
|
534 bundle manifest header. To work around this you should ship your plug-in with a |
|
535 bundle manifest. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=97689">97689</a>)</p> |
|
536 <h4>Location for Debug Options File on Mac OS</h4> |
|
537 <p>If you are running in debug mode on Mac OS, the default location for the |
|
538 .options file is inside the application bundle in the Eclipse.app/Contents/MacOS |
|
539 directory (like the eclipse.ini). (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88782">88782</a>)</p> |
|
540 |
|
541 <h4>Issues with JNI that use FindClass</h4> |
|
542 <p> |
|
543 There may be issues when using a JNI implementation that uses FindClass |
|
544 in a function where the JNIEnv pointer is not available, such as in a C |
|
545 callback (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=125250">125250</a>). The reason is that FindClass, in this case, uses the application |
|
546 class loader to find the class. |
|
547 If the desired class is in the classpath used for the application classloader |
|
548 (e.g. defined by the VM argument -cp <classpath>), as it would typically be in |
|
549 a stand-alone application, there is no problem. However, under |
|
550 Eclipse, the application classloader does not have access to classes |
|
551 contained in plug-ins. Eclipse uses its own class loader to find classes |
|
552 contained in plug-ins. |
|
553 </p> |
|
554 <p> |
|
555 The proper plug-in class loader is used by FindClass in JNI functions which are |
|
556 passed the JNIEnv pointer, but not when you have to use AttachCurrentThread to get the |
|
557 JNIEnv pointer. In this case the application classloader is used. |
|
558 </p> |
|
559 <p> |
|
560 For example, the following will fail because AttachCurrentThread is used to |
|
561 get the JNIEnv pointer:</p> |
|
562 <pre> |
|
563 static JavaVM* jvm; // Global variable |
|
564 |
|
565 void myCallback(void) { |
|
566 JNIEnv* env; |
|
567 jvm->AttachCurrentThread((void**)&env, NULL); |
|
568 // Fails if some/class is not in the application classloader: |
|
569 jclass cls = env->FindClass("some/class"); |
|
570 jmethodID methodID = env->GetMethodID(cls, "methodName", |
|
571 "(Ljava/lang/String;)V or whatever signature"); |
|
572 env->CallVoidMethod(callback, methodID, ...); |
|
573 jvm->DetachCurrentThread(); |
|
574 } |
|
575 } |
|
576 </pre> |
|
577 <p> |
|
578 A solution is to cache the method ID, for example: |
|
579 </p> |
|
580 <pre> |
|
581 static jmethodID mid; // Global variable |
|
582 |
|
583 JNIEXPORT jint JNICALL JNI_OnLoad(JavaVM *vm, void *reserved) { |
|
584 ... |
|
585 // Store the JavaVM pointer |
|
586 jvm = vm; |
|
587 |
|
588 // Find the class and store the method ID |
|
589 // Will use the class loader that loaded the JNI library |
|
590 jclass cls = env->FindClass(className"some/class"); |
|
591 if(!cls) goto ERR; |
|
592 |
|
593 mid = env->GetMethodID(cls, "methodName", |
|
594 "(Ljava/lang/String;)V or whatever signature"); |
|
595 if(!mid) goto ERR; |
|
596 ... |
|
597 } |
|
598 |
|
599 void myCallback(void) { |
|
600 JNIEnv* env; |
|
601 jvm->AttachCurrentThread((void**)&env, NULL); |
|
602 env->CallVoidMethod(callback, mid, ...); |
|
603 // Handle error ... |
|
604 jvm->DetachCurrentThread(); |
|
605 } |
|
606 } |
|
607 </pre> |
|
608 |
|
609 |
|
610 <h3>3.2.2 <a name="I-Platform-Ant">Platform - Ant</a></h3> |
|
611 <h4>UTF-8 encoded buildfiles with Byte Order Mark</h4> |
|
612 <p>UTF-8 encoded buildfiles with byte order marks will fail to be parsed correctly depending on the XML parser being used for the build. Therefore a valid buildfile will fail to build with an error message similar to: "BUILD FAILED: C:\workspace\bom.xml:1: Document root element is missing.". To succeed in building with these files, ensure to include Xerces jars on the Ant runtime classpath so that the Xerces parser is used to parse the XML. As well the context menu for these files in the Navigator or Package Explorer will not have the run shortcuts for Ant builds. (bug |
|
613 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=67048">67048</a>)</p> |
|
614 <h4> Custom Ant tasks and Ant |
|
615 types must be separate from plug-in library JARs</h4> |
|
616 <p>Including the class files for custom Ant tasks or Ant types in the regular |
|
617 code JAR for your plug-in causes problems. These class files must be provided in |
|
618 a separate JAR that is contributed to the <code>org.eclipse.ant.core.antTasks</code> |
|
619 or <code>antTypes</code> extension point (and not declared as a library in the |
|
620 plug-in's manifest). This ensures that the Ant tasks and types are loaded by the |
|
621 special Ant class loader and not by a plug-in classloader. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34466">34466</a>).</p> |
|
622 |
|
623 <h4> Concurrent Ant builds not supported</h4> |
|
624 <p>Eclipse can run Ant in the same JVM as the rest of Eclipse. Several aspects |
|
625 of Ant and its use of global Java resources (such as System.out and System.err), |
|
626 make it unsafe to run more than one Ant build concurrently in the same JVM. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=24129">24129</a>).</p> |
|
627 <h4> Running certain Ant tasks |
|
628 cause memory leakage</h4> |
|
629 <p>Certain Ant tasks are known to leak memory. Please see the bug report for |
|
630 details, patches, and possible workarounds. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=24448">24448</a>)</p> |
|
631 <h4> Tasks that require input |
|
632 lock up workspace</h4> |
|
633 |
|
634 <p>As with using Ant from the command line, prompts for input from the |
|
635 console is not handled. This is not the same as making use of the <input> |
|
636 task, which works correctly within Eclipse. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=21748">21748</a>)</p> |
|
637 <h4>"version" property is always set when running Ant in the same VM as Eclipse</h4> |
|
638 <p>The Xalan libraries set system properties including a version property. These get set as properties within the Ant build and therefore the "version" property cannot be set within an Ant buildfile due to the immutable nature of Ant properties. This property will always be set to "2.4.1" for Ant builds in the same VM as Eclipse. (bug |
|
639 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=45717">45717</a>)</p> |
|
640 <h4>XDoclet support from within Eclipse</h4> |
|
641 |
|
642 <p>Since there are differences when running Ant from the commandline and within Eclipse, some extra steps may be needed to have XDoclet support function correctly within Eclipse. Problems may occur creating XDoclet subtasks. The workarounds and full discussion can be found in bug report. (bug |
|
643 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37070">37070</a>)</p> |
|
644 <h4>Ant Editor code completion based on Ant 1.6.1</h4> |
|
645 <p>Code completion provided by the Ant editor does not respect the user-specified version of org.eclipse.ant.core plug-in or ANT_HOME. Code completion proposals are mostly based on Ant 1.6.1 with some updates to Ant 1.6.5 (bug |
|
646 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=30886">30886</a>)</p> |
|
647 <h4> Eclipse can hang due to implementation of the Ant <property> task (Windows 9X |
|
648 only)</h4> |
|
649 <p>On Windows 9X, using:<property environment="env"/> will cause Eclipse to hang if the build occurs in the same VM as Eclipse. Running the build in a separate VM will hang the build but not Eclipse. |
|
650 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=44196">44196</a>)</p> |
|
651 |
|
652 <h4> Setting build loggers not supported when debugging Ant builds</h4> |
|
653 <p>When debugging Ant builds within Eclipse, setting -logger as a program argument will be ignored.</p> |
|
654 |
|
655 <h4>Renaming an External Tool builder set to run during auto-build will cause errors</h4> |
|
656 <p>If you rename an existing external tool builder that is configured to run during auto-builds, you will get the following error: |
|
657 Errors during build. |
|
658 Errors running builder "Integrated External Tool Builder" on project |
|
659 <PROJECT_NAME>. |
|
660 The builder launch configuration could not be found. |
|
661 The workaround is to first disable the builder for auto-builds and then rename the builder. |
|
662 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=118294">118294</a>)</p> |
|
663 |
|
664 <h4>Slow typing/saving of the Ant editor with imports that define numerous macrodefs</h4> |
|
665 <p>The Ant editor is slow on saving with buildfiles that have <import> declarations of buildfiles that have numerous <macrodef>s. |
|
666 See bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92640">92640</a> and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=125117">125117</a> for possible workarounds</p> |
|
667 |
|
668 <h4>Failure to run Ant builds on non-Windows platforms if Eclipse installed in location with spaces in the path</h4> |
|
669 <p>Due to a bug in Ant 1.7.0, Ant builds will fail with an IllegalArgumentException if the Eclipse installation is in a location with spaces in the path. |
|
670 Embedded usage of Ant builds, such as plug-in export will also fail. |
|
671 See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=187993">187993</a> for possible workarounds</p> |
|
672 |
|
673 <h3>3.2.3 <a name="I-Platform-User-Assistance">Platform - User Assistance</a></h3> |
|
674 <h4>Welcome page not displayed properly (Linux/Unix)</h4> |
|
675 <p>The default Welcome implementation is HTML-based and requires a supported browser |
|
676 in order to work. If no supported browser can be found, Welcome falls back to its |
|
677 Forms-based implementation, which has a different (simpler) appearance. Consult the |
|
678 <a href="http://www.eclipse.org/swt/faq.php#browserplatforms">SWT FAQ</a> for supported |
|
679 browsers and setting up your browser to work with eclipse. |
|
680 </p> |
|
681 |
|
682 <h4>Help browser tool bar buttons do not work for some documents</h4> |
|
683 <p>The Help browser's Print, Synchronize, and Bookmark buttons do not work for |
|
684 pages that are not actually installed with the product. However, you can always |
|
685 use the print command in the browser's context menu to print the page you're |
|
686 reading. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=44216">44216</a>)</p> |
|
687 <h4> Help documents not displayed |
|
688 in a browser or very slow document loading (Windows only)</h4> |
|
689 |
|
690 If your LAN settings are not properly configured for local host access, your |
|
691 Help browser might open to a blank page or display an HTTP error instead of a |
|
692 help page, or you may experience long delays when loading help documents. Your |
|
693 system administrator can configure your LAN settings so that help documents can |
|
694 be accessed from the local help server. |
|
695 <blockquote> |
|
696 <ol> |
|
697 <li>In the Control Panel, open <b>Internet Options</b>, select the <b>Connections</b> |
|
698 tab and choose <b>LAN Settings</b>.</li> |
|
699 <li>If your host was configured to use DHCP for IP assignment, make sure |
|
700 that the "Automatically detect settings" check box is cleared.</li> |
|
701 <li>If you use a proxy server, ensure that the "Bypass proxy server |
|
702 for local addresses" is selected.</li> |
|
703 <li>In "Advanced" settings for proxies, add |
|
704 "127.0.0.1;localhost" to the "Exceptions" if these |
|
705 addresses are not listed.</li> |
|
706 <li>If you are using an automatic configuration script for proxy |
|
707 settings, and are not sure that the script is correct, clear the "Use |
|
708 automatic configuration script" check box.</li> |
|
709 |
|
710 </ol> |
|
711 </blockquote> |
|
712 <p>If the above steps do not fix your problem, try changing the port and host |
|
713 properties on the <b>Help > Help Server</b> preference page. In general, |
|
714 setting <code>host</code> to <code>localhost</code> or <code>127.0.0.1</code> |
|
715 |
|
716 should work. Also, especially when running a firewall, you may want to specify |
|
717 port 80 or some other firewall-friendly value. (bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=7036">7036</a>, |
|
718 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=9418">9418</a>, <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=11394">11394</a>)</p> |
|
719 <h4> Working disconnected from |
|
720 the network (Windows only)</h4> |
|
721 If you are experiencing problems when not connected to the network, you must |
|
722 install the loopback adapter from the Windows installation CD. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=831">831</a>) |
|
723 <h4> Using Internet Explorer in |
|
724 offline mode (Windows only)</h4> |
|
725 |
|
726 If you have been using Internet Explorer in Offline mode, when you access the |
|
727 help system you will get a message indicating that the web page you requested is |
|
728 not available offline or a blank page will display. Click <b>Connect</b> or |
|
729 deselect "Work Offline" in the Internet Explorer "File" menu |
|
730 to return the system behavior to normal. |
|
731 <h4>Help topics not highlighted in High Contrast mode (Windows only)</h4> |
|
732 <p>Windows High Contrast settings are not consistently picked up by Internet |
|
733 Explorer when they are set from the Accessibility Options utility as opposed to |
|
734 when they are set using the predefined schemes. On Windows XP, it is recommended |
|
735 to set High Contrast as follows: Right click the desktop, chose properties, |
|
736 select Windows Classic style from the Windows and buttons drop down on the |
|
737 Appearance tab, and choose your scheme (for example High Contrast Black) from |
|
738 Color Scheme drop down. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=28609">28609</a>)</p> |
|
739 <h4>Help browser displays a blank page</h4> |
|
740 |
|
741 <p>If you see a help launched with a blank page, and no errors displayed, it can |
|
742 be caused by a conflict between libraries in org.eclipse.tomcat plug-in and jars |
|
743 optionally installed in JRE jre/lib/ext directory. To fix the problem, ensure |
|
744 that the JRE used for running Eclipse does not contain any J2EE or Apache jars |
|
745 in the jre/lib/ext directory. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=63970">63970</a>)</p> |
|
746 |
|
747 <h3>3.2.4 <a name="I-Platform-UI">Platform - UI</a></h3> |
|
748 <h4>High contrast settings</h4> |
|
749 <p>Eclipse was tested for High Contrast using 1152 x 864 resolution in Windows |
|
750 XP High Contrast mode. You can select this mode by selecting Accessibility |
|
751 Options > Display > Use High Contrast from the Windows XP Control Panel |
|
752 menu.</p> |
|
753 <h4>Default text file encoding |
|
754 may be detected incorrectly (Windows XP/2000 only)</h4> |
|
755 |
|
756 <p><strong>Note</strong>: the bug report associated with this problem has been fixed. If you run Eclipse with JDK 1.5 or greater you should not have to use the workaround stated below any longer. However, the problem still exists when running Eclipse with JDK 1.4.x or lower, so in this case the workaround is still required . </p> |
|
757 <p>The "Text file encoding" value displayed in the Preferences |
|
758 dialog under "Editors" may be wrong on platforms running Windows XP |
|
759 (or 2000) when the user locale and system locale differ. </p> |
|
760 <p>Example of the manifestation of the bug: A Japanese user using Japanese |
|
761 Windows 2000 works in New York, United States. The user has selected English |
|
762 (United States) as the user locale. The "Text file encoding" value |
|
763 displayed by Eclipse is incorrect: "Cp1252" (English). It should |
|
764 display the system locale "MS932" (Japanese).</p> |
|
765 <p>Workaround: The user can modify the user locale so that user locale and |
|
766 system locale are identical. In the example above, this means the user should |
|
767 set Japanese as the user locale. Then restart Eclipse. The "Text file |
|
768 encoding" value will then be correct: "MS932" (Japanese).</p> |
|
769 |
|
770 <p>For Windows XP:</p> |
|
771 <ul> |
|
772 <li>To check the system locale: Open the Control Panel. Go to Regional and |
|
773 Language Options. Switch to the Advanced tab. The system locale is specified |
|
774 in "Language for non-Unicode programs".</li> |
|
775 <li>To change the user locale: Open the Control Panel. Go to Regional and |
|
776 Language Options. The user locale can be modified by changing the language |
|
777 in "Standards and formats".</li> |
|
778 </ul> |
|
779 <p>For Windows 2000:</p> |
|
780 <ul> |
|
781 <li>To check the system locale: Open the Control Panel. Go to Regional |
|
782 Options. Look up the items in the General tab, inside the "Language |
|
783 settings for the system" group. The system locale is the item marked as |
|
784 (Default).</li> |
|
785 <li>To change the user locale: Open the Control Panel. Go to Regional |
|
786 Options. The user locale can be modified by changing the location in |
|
787 "Settings for the current user".</li> |
|
788 |
|
789 </ul> |
|
790 <p>(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=20641">20641</a>)</p> |
|
791 <h4> Dirty state not tracked |
|
792 properly for OLE documents (Windows only)</h4> |
|
793 <p>The dirty state for an OLE document is not updated properly. This causes |
|
794 Eclipse to prompt to save the contents of the editor when the document is |
|
795 closed, even if the contents have already been saved. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=2564">2564</a>)</p> |
|
796 <h4> OLE document crashes can |
|
797 cause Eclipse to also crash (Windows only)</h4> |
|
798 <p>If an OLE document crashes, Eclipse can crash, or the workbench menus can |
|
799 become inconsistent.</p> |
|
800 <h4>2.1 Presentation based workspaces incorrectly get new Min/Max behavior</h4> |
|
801 <p> |
|
802 Workspaces that are currently using the Eclipse 2.1 Presentation will incorrectly |
|
803 'inherit' the new min/max behavior when opened with 3.3. |
|
804 </p> |
|
805 <p> |
|
806 Workaround:</p> |
|
807 <ol> |
|
808 <li>Go to the 'Preferences -> Appearance' page, change the current presentation to 'Default' and select apply</li> |
|
809 <li>Change it back to the 2.1 Presentation, select 'OK' and 'Yes' to the restart prompt</li> |
|
810 </ol> |
|
811 When the workbench re-opens the old min/max behavior will be restored. |
|
812 <h4>Toolbars only containing contributed controls exhibit display errors on Mac/Linux</h4> |
|
813 <p> |
|
814 Currently there is no way on the Max or Linux platforms to define the <b>height</b> for controls contributed to |
|
815 toolbars, nor will those platforms respect the size returned by the control's <code>computeSize</code> method. If you |
|
816 encounter this issue there is currently no truly viable workaround. |
|
817 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=183003">183003</a>) |
|
818 </p> |
|
819 |
|
820 |
|
821 <h3>3.2.5 <a name="I-Platform-Text">Platform - Text</a></h3> |
|
822 None. |
|
823 |
|
824 <h3>3.2.6 <a name="I-Platform-SWT">Platform - SWT</a></h3> |
|
825 <h4>Eclipse plug-in based on the SWT Browser throws exception</h4> |
|
826 <p>The SWT Browser widget uses a platform-specific web browser to render HTML. |
|
827 The org.eclipse.swt.SWTError exception ("No more handles") is thrown |
|
828 on platforms that don't meet the requirements for running the Browser widget. |
|
829 Supported platforms and prerequisites are listed on the SWT FAQ item <a href="http://www.eclipse.org/swt/faq.php#browserplatforms"> |
|
830 "Which platforms support the SWT Browser?"</a>.</p> |
|
831 |
|
832 <h4>Opening File Dialog crashes eclipse (Vista only)</h4> |
|
833 <p>On Vista, launching eclipse using <code>-vmargs -Xmx[any size]</code> can crash eclipse when the FileDialog is opened. |
|
834 The workaround is to use the default heap size, i.e. do not use the <code>-Xmx</code> VM args. |
|
835 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=188317">188317</a>)</p> |
|
836 |
|
837 <h4>Crash while editing text (Windows XP with SP2 only)</h4> |
|
838 <p>Some users who have installed Service Pack 2 on Windows XP have experienced |
|
839 crashes while using editors in Eclipse. The workaround is to place a working version |
|
840 of Windows\System32\USP10.DLL in the Eclipse startup directory or uninstall |
|
841 Service Pack 2. |
|
842 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=56390">56390</a>)</p> |
|
843 |
|
844 <h4>Input Method broken (Motif only)</h4> |
|
845 <p>Some versions of RedHat Linux such as Fedora Core 3 and Enterprise Linux WS |
|
846 release 4 use a new technology called IIIM (Intranet/Internet Input Method |
|
847 Framework) to replace the old XIM (X input method). When running on these |
|
848 new systems, Eclipse will crash if you attempt to enter any DBCS character. The |
|
849 workaround is to use a XIM based input method such as chinput. This problem |
|
850 may be fixed in newer releases of RedHat. |
|
851 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=89722">89722</a>)</p> |
|
852 |
|
853 <h4>Eclipse does not start on Linux-Motif with Xinerama and a UTF-8 locale</h4> |
|
854 <p>The Linux-motif build of Eclipse does not launch properly when run on a |
|
855 computer with Xinerama (provides support for dual head monitors) and a UTF-8 |
|
856 locale. The workaround for this problem is to change the locale to a non-UTF-8 |
|
857 value, or to disable Xinerama. |
|
858 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=38843">38843</a>) |
|
859 </p> |
|
860 |
|
861 <h4>Eclipse hangs when pasting from an unresponsive application (GTK only)</h4> |
|
862 <p>If the application that is supplying the clipboard material is unresponsive, |
|
863 the paste operation hangs Eclipse for several minutes. This situation can be |
|
864 encountered when copying from an Eclipse target workbench, suspending the target |
|
865 workbench at a breakpoint and pasting into the hosting Eclipse workbench. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=44915">44915</a>)</p> |
|
866 |
|
867 <h4>Unable to drag data between applications in simplified Chinese locale (Motif only)</h4> |
|
868 <p>When configured for the simplified Chinese locale, it is not possible to |
|
869 drag data between applications running on the Motif window system. This is a |
|
870 known limitation of the Open Motif library. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=29777">29777</a>)</p> |
|
871 |
|
872 <h4>Crash when attempting to launch file browser (AIX Motif only)</h4> |
|
873 <p>There is a known AIX graphics bug affecting certain levels of AIX |
|
874 releases. Ensure that the AIX install includes the necessary service updates as |
|
875 described in the "Install notes/requirements for Eclipse on AIX" |
|
876 attachment to Eclipse bug report number <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34524">34524</a>.</p> |
|
877 |
|
878 <h4>Available colors on 8-bit Linux (Linux only)</h4> |
|
879 <p>Typically, in Gnome Linux installs running with 8-bit visuals (i.e. 256 |
|
880 color mode), before the Eclipse application is started there are no free colors. |
|
881 This may mean that Eclipse is unable to allocate the default widget background |
|
882 color, causing it to display a white background. The functionality, however, is |
|
883 otherwise unaffected.</p> |
|
884 |
|
885 <h4>IME-related crash (Linux Motif only)</h4> |
|
886 <p>When using Linux Motif and GB18030 IME "chinput", Eclipse can |
|
887 crash if the IME client window is left open when the parent window is disposed. |
|
888 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32045">32045</a>)</p> |
|
889 |
|
890 <h4>IME conversion problem (Solaris GTK only)</h4> |
|
891 <p>When typing Japanese text, the conversion to Kanji must be done one ideogram at |
|
892 a time. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=226636">226636</a>)</p> |
|
893 |
|
894 <h4> gtk_init_check and X11 socket failure when using the IBM 1.4.2 JRE (GTK only)</h4> |
|
895 <p>Under RHEL 3.1 with the IBM 1.4.2 JRE and a large number |
|
896 of plugins, Eclipse may fail to launch with an exception from |
|
897 <tt>gtk_init_check</tt> along with this error:</p> |
|
898 <pre> |
|
899 _X11TransSocketOpen: socket() failed for local |
|
900 _X11TransSocketOpenCOTSClient: Unable to open socket for local |
|
901 </pre> |
|
902 <p>A workaround is to set the environment variable <tt>JAVA_HIGH_ZIPFDS</tt> to |
|
903 a value of 500 before starting Eclipse. (bug |
|
904 <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=106396">106396</a>)</p> |
|
905 |
|
906 <h4>Key bindings can stop working on Debian (GTK+ only)</h4> |
|
907 <p>On some versions of Debian, Eclipse key bindings may stop working. In this context |
|
908 the only way to make the key bindings work again is to restart Eclipse. |
|
909 </p><p> |
|
910 The problem is that a focus issue exists in GTK+ 2.6.7 and earlier, for which SWT has |
|
911 a workaround. This workaround is incompatible with the GTK+ 2.6.7 fix, so a GTK+ version |
|
912 check is done at runtime to determine whether the workaround should be used or not. |
|
913 However, Debian backported the GTK+ focus fix into their libgtk+2.0 (2.6.4-2) package, |
|
914 so the SWT workaround and GTK+ fix are both incorrectly applied in this context. |
|
915 </p><p> |
|
916 To work around this problem, either get the Debian unstable version of GTK+, compile your |
|
917 own GTK+, or hack SWT's Shell.gtk_realize(int) and change the version that it checks. |
|
918 See SWT bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=107013">107013</a> |
|
919 and GTK+ bug <a href="http://bugzilla.gnome.org/show_bug.cgi?id=109246">109246</a> |
|
920 for more information.</p> |
|
921 |
|
922 <h4>Typing in an editor crashes with IBM 1.5 VM (Linux GTK PPC only)</h4> |
|
923 <p>When running on the IBM Java 5.0 VM, Eclipse crashes while the user is typing in an editor. |
|
924 If using this VM you must disable the JIT with the -Xnojit vm argument to avoid the crashes |
|
925 (see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=116730">116730</a>). |
|
926 The command line for launching Eclipse with this vm should be: <br> |
|
927 <code>eclipse -vmargs -Dosgi.locking=none -Xnojit</code> |
|
928 </p> |
|
929 |
|
930 <h4>Eclipse won't start (Linux GTK PPC only)</h4> |
|
931 <p>Eclipse fails to create a lock file with reason "No locks available". |
|
932 To launch eclipse you must disable file locking using the osgi.locking property. |
|
933 For example, you could launch eclipse as follows: <br> |
|
934 <code>eclipse -vmargs -Dosgi.locking=none</code> |
|
935 </p> |
|
936 |
|
937 <h4>SWT for carbon cannot be used with OS X JRE version 1.6 (Mac OSX only)</h4> |
|
938 <p>OS X JRE version 1.6 assumes that pointers have a size of 64 bits, but SWT's Carbon |
|
939 port only uses 32-bit pointers, so SWT and Eclipse cannot be used with OS X JRE version |
|
940 1.6. The workaround is to use the cocoa version of SWT or an earlier supported version |
|
941 of the OS X JRE. |
|
942 </p> |
|
943 |
|
944 <h4>Strings may be truncated or incorrectly wrapped on RHEL5 (Linux GTK only)</h4> |
|
945 <p> |
|
946 Strings on wrapping Controls may not appear correctly in some locales on RHEL5 as a result |
|
947 of a bug in Pango version 1.14.x. This problem can be fixed by upgrading the installed |
|
948 Pango library to a version that is newer than 1.14.x. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=231951">231951</a>) |
|
949 </p> |
|
950 |
|
951 <h4>Block Selection functionality provided by StyledText is not BIDI aware</h4> |
|
952 <p> |
|
953 When the orientation of characters under the left and right edges of the block |
|
954 selection rectangle are not the same, the actual selection ranges (in memory) |
|
955 differ from the visual representation of the selection.(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=277929">277929</a>) |
|
956 </p> |
|
957 |
|
958 |
|
959 <h3>3.2.7 <a name="I-Platform-Team-CVS">Platform - Team - CVS</a></h3> |
|
960 <p>The following are known problems with the CVS repository provider only, and |
|
961 do not apply to other repository providers. Additional information on how to use |
|
962 CVS from Eclipse can be found in the <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-vcm-home/docs/online/cvs_features2.0/cvs-faq.html">Eclipse |
|
963 CVS FAQ</a>.</p> |
|
964 <h4> CVS server compatibility</h4> |
|
965 <p>The CVS plug-in parses messages returned from the CVS server. If the format |
|
966 of these messages is not as expected, some of the plug-in's functionality may be |
|
967 missing. The CVS plug-in is compatible with all stable 1.11.X builds of the CVS |
|
968 server, and should be compatible with future releases in that stream unless text |
|
969 message formats change (the last tested server was 1.11.22). As for the 1.12.X |
|
970 feature releases of CVS, the Eclipse CVS client has been tested with builds up |
|
971 to 1.12.13. However, future releases could easily break the Eclipse CVS client. |
|
972 Basic functionality, such as Checkout, Commit, and Update, should always work, |
|
973 but there may be problems with more advanced commands such as Synchronizing and |
|
974 Browsing the repository.</p> |
|
975 |
|
976 <h4>SSH2 proxy settings lost upgrading to 3.3</h4> |
|
977 <p>CVS now uses the Platform proxy settings. As a result, any CVS proxy settings |
|
978 will be lost and must be re-entered on the General>Network Connections preference |
|
979 page. </p> |
|
980 <h4>Connection cannot be found after initially missing</h4> |
|
981 <p>If a connection initially fails due to a network problem, the connection may |
|
982 continue to fail even when the network problem is fixed. In order to establish |
|
983 the connection you must exit and restart Eclipse. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=9295">9295</a>)</p> |
|
984 <h4>"Received broken pipe signal" error from server</h4> |
|
985 <p>Eclipse sometimes performs multiple commands within a single connection to |
|
986 the server. This may cause problems with CVS servers that are running server |
|
987 scripts in response to certain commands. (bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=23575">23575</a> |
|
988 and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=23581">23581</a>)</p> |
|
989 |
|
990 <h4>"Terminated with fatal signal 10" error from server</h4> |
|
991 <p>There is a bug in the CVS server related to some compression levels. If you |
|
992 get this error, changing the compression level on the CVS preference page may |
|
993 help. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=15724">15724</a>)</p> |
|
994 <h4>"Unknown response" error using ext connection method</h4> |
|
995 <p>There are a few situations that can result in an "Unknown response" |
|
996 error messages when using the ext connection method. One situation involves |
|
997 using an external communications client (e.g. rsh or ssh) that adds CRs to the |
|
998 communications channel (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=21180">21180</a>). |
|
999 Another involves Eclipse not properly reading the stderr output of the external |
|
1000 communications tool. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=11633">11633</a>)</p> |
|
1001 |
|
1002 <h4>A disabled CVS capability may not be auto-enabled in existing workspaces</h4> |
|
1003 <p>New in 3.0 is the ability to disable capabilities and the CVS support in |
|
1004 Eclipse can be disabled. However, for backwards compatibility the CVS capability |
|
1005 is auto-enabled in existing workspaces that already contain CVS projects. The |
|
1006 auto-enabling function may not run if the team support plugin is not loaded at |
|
1007 startup. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66977">66977</a>)</p> |
|
1008 <h4>Builder output files may appear as changed</h4> |
|
1009 <p>When folders containing build output are shared they may get improperly |
|
1010 marked as dirty when build output is generated.</p> |
|
1011 |
|
1012 <h4>Enabling GNOME proxy support</h4> |
|
1013 <p>GNOME applications can make use of proxy settings defined in this environment. |
|
1014 If set, Eclipse will use it prior to proxy settings declared using env variables. |
|
1015 This feature is disabled by default, to enable it launch Eclipse with |
|
1016 <code>"-Dorg.eclipse.core.net.enableGnome"</code> switch. That is,</p> |
|
1017 <pre>eclipse -Dorg.eclipse.core.net.enableGnome</pre> |
|
1018 |
|
1019 <h3>3.2.8 <a name="I-Platform-Install-Update">Platform - Install/Update</a></h3> |
|
1020 <h4>Manually installing features and plug-ins on a FAT file system (Windows only)</h4> |
|
1021 |
|
1022 <p>When features and plug-ins are manually installed on top of an Eclipse-based |
|
1023 product install located on a FAT file system that has already been run at least |
|
1024 once, the product must be explicitly restarted with -clean. That is,</p> |
|
1025 <pre>eclipse.exe -clean |
|
1026 </pre> |
|
1027 |
|
1028 <h4>Connecting to untrusted sites using https</h4> |
|
1029 <p>You cannot install or update software from a site using https whose certificate |
|
1030 is not chained to a trusted root certificate in your local certificate store. This typically |
|
1031 means the server is using a self-signed certificate, or a certificate authenticated by |
|
1032 an unknown third party.</p> |
|
1033 |
|
1034 <h4>Extension location is lost if the install path changes</h4> |
|
1035 <P>A previously configured extension location may be temporarily removed if the install is moved or mounted |
|
1036 under a different path. This only happens when the link file that configures the |
|
1037 extension location uses a relative path that points to a directory under the Eclipse |
|
1038 install. On a second startup using the same install path, the extension location |
|
1039 is added again (bug <A HREF="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95403">95403</A>). <BR></P> |
|
1040 |
|
1041 <h4>Feature patches can only be installed from Eclipse 3.4-based update sites</h4> |
|
1042 <p>Feature patches can only be installed from update sites designed for Eclipse 3.4 or greater. |
|
1043 Specifically, the update site must have the necessary metadata for Equinox p2 (a content.xml |
|
1044 or content.jar file). This data can be generated by building an update site using Eclipse 3.4 |
|
1045 or newer, or running the p2 metadata generator on an update site built using earlier versions |
|
1046 of the Eclipse SDK. See the help topic <i>Generating p2 metadata</i> for more details on running the p2 metadata |
|
1047 generator (bug <A HREF="https://bugs.eclipse.org/bugs/show_bug.cgi?id=244483">244483</A>). |
|
1048 </p> |
|
1049 |
|
1050 <h3>3.2.9 <a name="I-Platform-Debug">Platform - Debug</a></h3> |
|
1051 <p>None. (Known problems with the Java debugger appear below in the <a href="#I-JDT">JDT</a> |
|
1052 section.)</p> |
|
1053 |
|
1054 <h3>3.2.10 <a name="I-Platform-Compare">Platform - Compare</a></h3> |
|
1055 <p>None.</p> |
|
1056 |
|
1057 <h3>3.3 <a name="I-JDT">Java development tools (JDT)</a></h3> |
|
1058 |
|
1059 <h4>Multiple regions formatting in a given source snippet</h4> |
|
1060 In version 3.4, the new API method <code>org.eclipse.jdt.core.formatter.CodeFormatter.format(int, String, IRegion[], int, String)</code> |
|
1061 has been added to allow the formatting of several regions in a source snippet with a single pass.<br> |
|
1062 Even if specified, this method does not currently accept comments of the following kinds: |
|
1063 <ul> |
|
1064 <li><code>org.eclipse.jdt.core.formatter.CodeFormatter#K_SINGLE_LINE_COMMENT</code></li> |
|
1065 <li><code>org.eclipse.jdt.core.formatter.CodeFormatter#K_MULTI_LINE_COMMENT</code></li> |
|
1066 <li><code>org.eclipse.jdt.core.formatter.CodeFormatter#K_JAVA_DOC</code></li> |
|
1067 </ul> |
|
1068 This will be fixed in a future release (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=233967">233967</a>). |
|
1069 |
|
1070 <h4>Searching for constant field references</h4> |
|
1071 <p>Search does not find references to constant fields inside binaries because |
|
1072 the Java Language Specification mandates that constant field values be inlined |
|
1073 in the class file's byte codes, leaving no trace of a field reference. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=12044">12044</a>)</p> |
|
1074 |
|
1075 <h4> Cut, copy, paste not working |
|
1076 for linked resources in views showing Java elements</h4> |
|
1077 <p>The cut, copy, and paste actions do not work for linked files and folders |
|
1078 appearing in views that show Java elements, including the Package Explorer. The |
|
1079 workaround is to use these actions from the Navigator view instead. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34568">34568</a>)</p> |
|
1080 <h4> Java working sets not |
|
1081 working correctly for elements from JRE system library container</h4> |
|
1082 <p>Applying a working set consisting entirely of elements from the JRE System |
|
1083 library container as a filter to the packages view might result in an empty |
|
1084 Package Explorer. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=30442">30442</a>)</p> |
|
1085 |
|
1086 <h4>Breakpoints unreliable running Sun 1.6.0_14</h4> |
|
1087 Developers debugging applications on Sun's 1.6.0_14 |
|
1088 virtual machine should be aware that breakpoints are unreliable (i.e. do |
|
1089 not always suspend execution). The problem occurs on Windows and Linux |
|
1090 platforms. At this point, it appears to be an issue with the VM rather than Eclipse. |
|
1091 The workaround is to use the 1.6.0_13 virtual machine. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=279137">279137</a>). |
|
1092 |
|
1093 <h4>Side effects of Step into Selection and Run to Line</h4> |
|
1094 <p>The actions "Step into Selection" and "Run to Line" |
|
1095 optimistically set breakpoints on the line the user has chosen to step into or |
|
1096 run to. However, the debugger can not determine if or when execution will ever |
|
1097 reach the chosen line. The breakpoints set by the underlying implementation are |
|
1098 not visible to the user and can cause execution to suspend unexpectedly at a |
|
1099 later time, when the associated line is actually executed. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=51507">51507</a>)</p> |
|
1100 |
|
1101 <h4>Default locale initialization incorrect</h4> |
|
1102 <p>The default locale is generally initialized from the settings in the |
|
1103 operating system when a target VM is launched. However, when using javaw.exe on |
|
1104 JDK1.4.2, Windows XP, the default locale is incorrectly initialized to en_US, no |
|
1105 matter what the operating system settings are. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=65945">65945</a>)</p> |
|
1106 |
|
1107 <h4>Some refactoring script operations fail with Sun 6.0 JREs</h4> |
|
1108 <p>Creating and applying refactoring scripts sometimes fails with Sun 6.0 JREs |
|
1109 due to a bug in the XML parser that is shipped with those VMs. |
|
1110 A workaround is to use a J2SE 5.0 VM or an IBM 6.0 VM. |
|
1111 Another workaround is to replace the XML parser using the |
|
1112 <a href="http://java.sun.com/javase/6/docs/technotes/guides/standards/index.html">Java Endorsed Standards Override Mechanism</a>: |
|
1113 </p> |
|
1114 <ol> |
|
1115 <li>Get original versions of xml-apis.jar, xercesImpl.jar, xalan.jar, and serializer.jar from Apache, e.g. |
|
1116 xalan-j_2_7_1-bin.zip from <a href="http://xml.apache.org/xalan-j/downloads.html">here</a>. |
|
1117 </li> |
|
1118 <li>Unpack the archive and copy the 4 JARs into <code><path-to-your-JavaSE6.0-install>\jre\lib\endorsed\</code>. |
|
1119 </li> |
|
1120 </ol> |
|
1121 (see Sun bug <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6760982">http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6760982</a>, |
|
1122 Eclipse bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=262820">262820</a>) |
|
1123 |
|
1124 <h4>Suspend on uncaught exception overrides exception breakpoint location filters</h4> |
|
1125 <p>Exception breakpoints can be configured with location filters (inclusive and |
|
1126 exclusive). When an unchecked exception is configured to <b>not</b> suspend |
|
1127 execution in a specific class, execution will still suspend when the user preference |
|
1128 to suspend on uncaught exceptions is on. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66770">66770</a>)</p> |
|
1129 |
|
1130 <h4>Running Java programs with non-Latin-1 characters in package or class names</h4> |
|
1131 You get a <code>java.lang.NoClassDefFoundError</code> when running Java |
|
1132 programs with non-Latin characters in the package or class names. The workaround |
|
1133 is to package the class files as a JAR file and run the program out of the JAR |
|
1134 and not from the file system directly. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=4181">4181</a>) |
|
1135 |
|
1136 <h4>Cannot run or debug class in |
|
1137 a project with GB18030 characters in project name</h4> |
|
1138 <p>Most class libraries do not properly support the creation of a system |
|
1139 process (via <code>java.lang.Runtime.exec(...)</code>) when the specified |
|
1140 command line contains GB18030 characters. This limitation means the debugger |
|
1141 cannot launch applications when the command line it generates contains GB18030 |
|
1142 characters. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32206">32206</a>)</p> |
|
1143 |
|
1144 <h4>Cannot detect installed JRE with GB18030 characters in path name</h4> |
|
1145 <p>Automatic JRE detection fails when the JRE is stored in a directory |
|
1146 containing GB18030 characters in its name. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=33844">33844</a>)</p> |
|
1147 |
|
1148 <h4>Cannot generate Javadoc for packages with GB18030 characters in the name</h4> |
|
1149 <p>Most class libraries do not properly support the creation of a system |
|
1150 process (via <code>java.lang.Runtime.exec(...)</code>) when the specified |
|
1151 command line contains GB18030 characters. Since Javadoc is created using the |
|
1152 Javadoc executable provided with the JDK, generating Javadoc fails if the |
|
1153 package or class name contains GB18030 characters. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32215">32215</a>)</p> |
|
1154 |
|
1155 <h4> Unable to debug stack |
|
1156 overflows</h4> |
|
1157 |
|
1158 <p>If a debug session suspends on a <code>java.lang.StackOverflowError</code> |
|
1159 exception (due to an exception breakpoint), the debugger may not be able to |
|
1160 retrieve any debug information from the target JVM. As well, the debugger may |
|
1161 not be able to reliably interact with the target JVM past this point. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=19217">19217</a>)</p> |
|
1162 <h4> Evaluation limitation</h4> |
|
1163 <p>The debugger uses threads in the target JVM to perform evaluations (both |
|
1164 explicit evaluations that the user requests, and implicit evaluations such as <code>toString()</code> |
|
1165 invocations in the <b>Variables</b> view). The Java Debug Interface (JDI) |
|
1166 requires that the thread in which an evaluation is performed be suspended by a |
|
1167 user event (that is, a breakpoint or step request). Evaluations cannot be |
|
1168 performed on threads suspended by the suspend action. As well, when a breakpoint |
|
1169 is configured to suspend the JVM rather than just the individual thread, the |
|
1170 threads which did not encounter the breakpoint are not in a valid state to |
|
1171 perform an evaluation. When an evaluation is attempted in a thread that is not |
|
1172 in a valid state to perform an evaluation, an error message will appear to the |
|
1173 effect of "Thread must be suspended by step or breakpoint to perform method |
|
1174 invocation". (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34440">34440</a>)</p> |
|
1175 |
|
1176 <h4> Missing debug attributes</h4> |
|
1177 The debugger requires that class files be compiled with debug attributes if |
|
1178 it is to be able to display line numbers and local variables. Quite often, class |
|
1179 libraries (for example, "<code>rt.jar</code>") are compiled without |
|
1180 complete debug attributes, and thus local variables and method arguments for |
|
1181 those classes are not visible in the debugger. |
|
1182 <h4> Using Hot Code Replace</h4> |
|
1183 <p>Hot code replace is supported on JDK 1.4.x VMs, and IBM J9 VMs. The debugger |
|
1184 will attempt to replace all class files that change in the workspace as the user |
|
1185 edits and builds source code. However, hot code replace is limited to changes |
|
1186 that a particular virtual machine implementation supports. For example, changes |
|
1187 within existing methods may be supported, but the addition or removal of members |
|
1188 may not be.</p> |
|
1189 <p>Note that hot code replace and stepping on JDK 1.4.0 VMs was unreliable. The |
|
1190 underlying VM problems were fixed in JDK 1.4.1, and later.</p> |
|
1191 <h4> Scrapbook</h4> |
|
1192 Setting a breakpoint inside a scrapbook page is not supported. |
|
1193 |
|
1194 <p>When a snippet is run in the scrapbook which directly or indirectly calls <code>System.exit(int)</code>, |
|
1195 the evaluation cannot be completed, and will result in a stack trace for a <code>com.sun.jdi.VMDisconnectedException</code> |
|
1196 being displayed in the scrapbook editor.</p> |
|
1197 <p>Terminating a scrapbook page while it is performing an evaluation results |
|
1198 in a <code>com.sun.jdi.VMDisconnectedException</code> being displayed in the |
|
1199 scrapbook editor.</p> |
|
1200 <h4> Debugging over slow |
|
1201 connections</h4> |
|
1202 A global Java debug preference specifies the debugger timeout, which is the |
|
1203 maximum amount of time the debugger waits for a response from the target VM |
|
1204 after making a request of that VM. Slow connections may require that this value |
|
1205 be increased. The timeout value can be edited from the <b>Java > Debug </b>preference |
|
1206 page. Changing the timeout value only effects subsequently launched VM, not VMs |
|
1207 that are already running. |
|
1208 |
|
1209 <h4> Updating of inspected values</h4> |
|
1210 When inspecting the result of an evaluated expression in the debugger, it is |
|
1211 important to note that the result displayed is the result of that expression at |
|
1212 the time it was evaluated. For example, when inspecting a simple integer counter |
|
1213 (primitive data type), the value displayed in the Expressions view is the value |
|
1214 when the expression was evaluated. As the counter is changed in the running |
|
1215 program, the inspected result will not change (since the view is not displaying |
|
1216 the value bound to a variable - it is displaying the value of an expression, and |
|
1217 the value of a primitive data type cannot change). However, if an expression |
|
1218 results in an object, fields of that object will be updated in the inspector as |
|
1219 they change in the running program (since the value bound to fields in an object |
|
1220 can change). |
|
1221 <h4> Stepping over native methods |
|
1222 that perform I/O</h4> |
|
1223 When the debugger steps over native methods that perform I/O to <code>System.out</code> |
|
1224 or <code>System.err</code>, the output may not appear immediately unless the |
|
1225 native performs a flush on the output buffer. |
|
1226 <h4> VM and process termination |
|
1227 running on IBM 1.3 JVM on Linux (Linux only)</h4> |
|
1228 Terminating a launch, debug target, or system process associated with a debug |
|
1229 target running on the IBM 1.3 JVM on the Linux platform does not work when the |
|
1230 associated debug target has a suspended thread. To remove such debug targets |
|
1231 from the debug UI, select <b>Terminate and Remove</b> from the debug view's |
|
1232 pop-up menu (or use the shortcut "delete" key). Associated system |
|
1233 processes in the OS may not be properly cleaned up. If a debug target has no |
|
1234 suspended threads, termination works properly. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=1631">1631</a>) |
|
1235 |
|
1236 |
|
1237 <h4> Memory View (Linux only)</h4> |
|
1238 The feature to automatically load segments of memory while scrolling in the Memory |
|
1239 view does not work on Linux. Instead the user must use the "Next Page" and "Previous Page" actions |
|
1240 to manually load memory segments (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=74559">74559</a>) |
|
1241 <h4>Java 6 and MacOS</h4> |
|
1242 Apple JavaSE-1.6 VMs only execute on 64-bit architectures but JDT will detect 1.6 VMs installed on 32-bit |
|
1243 architectures when a new workspace is started or when the user presses the "Search..." button |
|
1244 on the Installed JREs preference page. Error messages will appear in the log each time JDT attempts to |
|
1245 determine which execution environments a 1.6 VM is compatible with. JDT can be configured to ignore 1.6 |
|
1246 JREs by removing them from the Installed JREs preference page. |
|
1247 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=262542">262542</a>) |
|
1248 <h4>Java 6 Annotation Processing</h4> |
|
1249 Java 6 annotation processors are supported in the batch compiler and in the IDE, with |
|
1250 some limitations. Java 6 processors are only executed during a build, not while editing (bug |
|
1251 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=188558">188558</a>). Some methods |
|
1252 in the processing API are unimplemented when compiling within the IDE, and will throw |
|
1253 UnsupportedOperationException. |
|
1254 |
|
1255 <h3>3.4 <a name="I-PDE">Plug-in Development Environment (PDE)</a></h3> |
|
1256 <h4>Feature manifest editor does not preserve all comments</h4> |
|
1257 |
|
1258 <p>When a non-source page of the feature manifest editor is used, PDE will convert |
|
1259 changes back into XML by regenerating the file. Although the overall content and |
|
1260 most of the comments are preserved, some comments may be lost. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=59502">59502</a>)</p> |
|
1261 <h4>PDE will not unzip source zips of some plug-ins</h4> |
|
1262 <p>In the plug-in import wizard, when you choose to import plug-ins as |
|
1263 "projects with source folders", PDE will not unzip the source for the |
|
1264 org.apache.ant, org.eclipse.core.runtime.compatibility.registry, org.eclipse.osgi.util and org.eclipse.osgi.services. This is |
|
1265 because the source ZIPs contains code that will not compile when unzipped as it |
|
1266 requires additional JARs that are not part of the SDK. To avoid the creation of |
|
1267 plug-in projects that won't compile, PDE will import these plug-ins as binary |
|
1268 and attach source, so you would still be able to read the source, you just won't |
|
1269 be able to modify it. Also, PDE will not unzip the source for the |
|
1270 org.eclipse.swt plug-ins. In this case, it is because, when shipped, the swt |
|
1271 code is spread across a plug-in and a fragment, and when unzipped, it will |
|
1272 require circular dependencies between the plug-in and fragment projects. These |
|
1273 circular dependencies are at minimum marked as warnings by the JDT compiler and |
|
1274 may result in unpredictable build behavior. Therefore, PDE always imports |
|
1275 org.eclipse.swt as binary with source attached. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66314">66314</a>)</p> |
|
1276 |
|
1277 <h4>Emacs key bindings do not |
|
1278 work in manifest editor fields</h4> |
|
1279 <p>Non-default key bindings currently do not work in fields on non-source |
|
1280 pages of the PDE manifest editors. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=19482">19482</a>)</p> |
|
1281 <h4>Plug-in import wizard does |
|
1282 not allow plug-ins of different versions to be imported</h4> |
|
1283 <p>The Eclipse platform allows two plug-ins with the same ID but different |
|
1284 versions to coexist if the only thing they contribute is run-time libraries. |
|
1285 However, PDE cannot handle these plug-ins because it creates project names using |
|
1286 plug-in Ids during binary project import. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=18500">18500</a>)</p> |
|
1287 <h4>Export of plug-in may silently drop classes</h4> |
|
1288 <p>When exporting a plug-in using the plug-in, feature or product wizards, some classes |
|
1289 might be dropped from the resulting archive if their fully qualified name is too long. |
|
1290 This typical path limitation can be worked around by creating the jar of the problematic |
|
1291 plug-in by using the Jar export wizard. |
|
1292 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=97150">97150</a>)</p> |
|
1293 |
|
1294 <h4>Compilation errors when exporting projects not stored outside of the workspace</h4> |
|
1295 <p>When exporting multiple plug-ins and one is stored outside of the workspace, |
|
1296 compile errors occurs on export. To work around the problem, you can either export |
|
1297 the plug-ins one by one, or change their location. |
|
1298 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=98579">98579</a>)</p> |
|
1299 |
|
1300 <h4>Headless build needs to be run from a fully qualified path</h4> |
|
1301 <p>When running a headless build using the scripts provided by pde build, the properties <code>builder</code> |
|
1302 and <code>buildDirectory</code> must refer to a fully qualified path. |
|
1303 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139554">139554</a>) |
|
1304 </p> |
|
1305 |
|
1306 <h4>Target Platform only sees installed plug-ins</h4> |
|
1307 <p>With the new p2 provisioning system in 3.4, PDE introduced a preference to control how target platforms are built. |
|
1308 By default, this preference is on if your target equals your host, otherwise it's off. When this preference is enabled, PDE attempts to |
|
1309 read a target platform's configuration and build the target platform based in the target's list of installed plug-ins. If a configuration |
|
1310 can't be found (a bundles.info or platform.xml file), PDE will simply manually scan the target directory and populate the target platform's |
|
1311 list of plug-ins. |
|
1312 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=226037">226037</a> and bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=225148">225148</a>) |
|
1313 </p> |
|
1314 |
|
1315 <h4>Delta pack is not seen by PDE when installed</h4> |
|
1316 <p>If you're using the delta pack, the target platform preference for building a target based on the target's installed plug-ins must be checked off. |
|
1317 This is because a target's runtime configuration only contains plug-ins specific to the platform it's running on. |
|
1318 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=230146">230146</a>) |
|
1319 </p> |
|
1320 |
|
1321 <h4>The org.osgi.util.tracker package is exported at wrong version</h4> |
|
1322 <p>The Equinox OSGI Framework (org.eclipse.osgi) exports the org.osgi.util.tracker package |
|
1323 at the incorrect version of 1.4.2. The correct org.osgi.util.tracker package version for |
|
1324 the OSGi Release 4 Version 4.2 specification is version 1.4.0. Bundles that |
|
1325 wish to run on other vendor frameworks should import the org.osgi.util.tracker package at |
|
1326 version 1.4.0. By default PDE will suggest the version 1.4.2 to be used when a bundle imports |
|
1327 the org.osgi.util.tracker package (using Import-Package manifest header). Developers can |
|
1328 manually change the import to use 1.4.0 version of the package to be able to run on both |
|
1329 Equinox and other vendor frameworks. |
|
1330 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=279622">279622</a>) |
|
1331 </p> |
|
1332 |
|
1333 <h2>4. <a name="Running Eclipse">Running Eclipse</a></h2> |
|
1334 <p>After installing the Eclipse SDK in a directory, you can start the Workbench |
|
1335 by running the Eclipse executable included with the release (you also need a 1.4.2 |
|
1336 JRE, not included with the Eclipse SDK). On Windows, the executable file is called <samp>eclipse.exe</samp>, |
|
1337 and is located in the <code>eclipse</code> sub-directory of the install. If |
|
1338 installed at <code>c:\eclipse-SDK-3.5-win32</code>, the executable is <code>c:\eclipse-SDK-3.5-win32\eclipse\eclipse.exe</code>. |
|
1339 |
|
1340 <b>Note:</b> Set-up on most other operating environments is analogous. Special |
|
1341 instructions for Mac OS X are listed <a href="#macosx">below</a>.</p> |
|
1342 |
|
1343 <h3>Allocating enough memory and solving OutOfMemoryErrors</h3> |
|
1344 <p>By default, Eclipse will allocate up to 256 megabytes of Java heap memory. This should |
|
1345 be ample for all typical development tasks. However, depending on the JRE |
|
1346 that you are running, the number of additional plug-ins you are using, and |
|
1347 the number of files you will be working with, you could conceivably have to increase this amount. |
|
1348 Eclipse allows you to pass arguments directly to the Java VM using the |
|
1349 <code>-vmargs</code> command line argument, which must follow all other Eclipse specific arguments. |
|
1350 Thus, to increase the available heap memory, you would typically use:</p> |
|
1351 <blockquote> |
|
1352 <p><code>eclipse -vmargs -Xmx<memory size></code></p> |
|
1353 </blockquote> |
|
1354 <p>with the <code><memory size></code> value set to greater than |
|
1355 "256M" (256 megabytes -- the default). |
|
1356 </p> |
|
1357 <p> |
|
1358 When using a Sun VM, you may also need to increase the size of the permanent |
|
1359 generation memory. The default maximum is 64 megabytes, but more may |
|
1360 be needed depending on your plug-in configuration and use. When the VM runs |
|
1361 out of permanent generation memory, it may crash or hang during class loading. |
|
1362 This failure is less common when using Sun JRE version 1.5.0_07 or greater. |
|
1363 The maximum permanent generation size is increased using the -XX:MaxPermSize=<memory size> argument:</p> |
|
1364 <blockquote> |
|
1365 <p><code>eclipse -vmargs -XX:MaxPermSize=<memory size></code></p> |
|
1366 </blockquote> |
|
1367 <p>This argument may not be available for all VM versions and platforms; consult your VM documentation |
|
1368 for more details. |
|
1369 </p> |
|
1370 <p> |
|
1371 Note that setting memory sizes to be larger than the amount of available physical |
|
1372 memory on your machine will cause Java to "thrash" as it copies objects |
|
1373 back and forth to virtual memory, which will severely degrade your performance. |
|
1374 </p> |
|
1375 <h3>Selecting a workspace</h3> |
|
1376 <p>When the Workbench is launched, the first thing you see is a |
|
1377 dialog that allows you to select where the workspace will be located. The |
|
1378 workspace is the directory where your work will be stored. |
|
1379 If you do not specify otherwise, Eclipse creates the workspace in your |
|
1380 user directory. |
|
1381 This workspace directory is used as the default content area for your projects |
|
1382 as well as for holding any required metadata. For shared or multi-workspace |
|
1383 installs you must explicitly specify the location for your workspace using the |
|
1384 dialog (or via the "<code>-data</code>" command line argument).</p> |
|
1385 <h3>Specifying the Java virtual machine</h3> |
|
1386 <p>Here is a typical Eclipse command line: </p> |
|
1387 |
|
1388 <blockquote> |
|
1389 <p><code>eclipse -vm c:\jdk1.4.2\jre\bin\javaw</code></p> |
|
1390 </blockquote> |
|
1391 <p><i>Tip:</i> It's generally a good idea to explicitly specify which Java VM to |
|
1392 use when running Eclipse. This is achieved with the "<code>-vm</code>" |
|
1393 command line argument as illustrated above. If you don't use "<code>-vm</code>", |
|
1394 Eclipse will look on the O/S path. When you install other Java-based products, |
|
1395 they may change your path and could result in a different Java VM being used |
|
1396 when you next launch Eclipse.</p> |
|
1397 <p>To create a Windows shortcut to an installed Eclipse:</p> |
|
1398 <ol> |
|
1399 <li>Navigate to <code>eclipse.exe</code> in Windows Explorer and use Create |
|
1400 Shortcut on the content menu.</li> |
|
1401 <li>Select the shortcut and edit its Properties. In the Target: field append |
|
1402 the command line arguments.</li> |
|
1403 </ol> |
|
1404 <p>Opening this shortcut launches Eclipse. (You can drag the shortcut to the |
|
1405 Windows Desktop if you want to keep it in easy reach.)</p> |
|
1406 |
|
1407 <h3><a name="macosx">Mac OS X</a></h3> |
|
1408 <p>On Mac OS X, you start Eclipse by double clicking the Eclipse application. If you need to |
|
1409 pass arguments to Eclipse, you'll have to edit the <code>eclipse.ini</code> file |
|
1410 inside the Eclipse application bundle: select the Eclipse application bundle icon while holding down the Control Key. |
|
1411 This will present you with a popup menu. Select "Show Package Contents" in the popup menu. |
|
1412 Locate <code>eclipse.ini</code> file in the <code>Contents/MacOS</code> sub-folder and open it with your favorite text editor to edit the command line options. |
|
1413 </p> |
|
1414 |
|
1415 <p> |
|
1416 On MacOS X you can only launch a UI program more than once if you have separate |
|
1417 copies of the program on disk. The reason for this behavior is that every UI |
|
1418 application on Mac can open multiple documents, so typically there is no need |
|
1419 to open a program twice. Since Eclipse cannot open more than one workspace, this means you have to make |
|
1420 a copy of the Eclipse install if you want to open more then one workspace at |
|
1421 the same time (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139319">139319</a>). |
|
1422 </p> |
|
1423 |
|
1424 <p>If you need to launch Eclipse from the command line, you can use the symbolic link "eclipse" in the |
|
1425 top-level eclipse folder. It refers to the eclipse executable inside the application bundle and takes |
|
1426 the same arguments as "eclipse.exe" on other platforms. |
|
1427 </p> |
|
1428 <p>On Mac OS X 10.4 and later, you may notice a slow down when working with significant |
|
1429 numbers of resources if you allow Spotlight to index your workspace. To prevent this, start |
|
1430 System Preferences, select the Spotlight icon, then the Privacy tab, then click the Add button |
|
1431 ("+") and find your workspace directory in the dialog that appears.</p> |
|
1432 <h3><a name="SharedInstall">Shared Install</a></h3> |
|
1433 <p>The startup speed of a shared install can be improved if proper cache information is stored in the shared |
|
1434 install area. To achieve this, after unzipping Eclipse distribution, run Eclipse once with the "-initialize" |
|
1435 option from an account that has a write access to the install directory.</p> |
|
1436 <h2>5. <a name="Upgrading"></a>Upgrading Workspace from a Previous Release</h2> |
|
1437 |
|
1438 <h3>Users who don't use "-data"</h3> |
|
1439 <p>If you weren't previously using "-data" to specify your workspace, |
|
1440 follow these steps to upgrade:</p> |
|
1441 |
|
1442 <ol> |
|
1443 <li>Find the workspace directory used by your old version of Eclipse. |
|
1444 Typically this is located inside the directory in which Eclipse was |
|
1445 installed in a sub-directory called "<code>workspace</code>". If |
|
1446 you are using a shortcut or script to launch Eclipse, then it will be under |
|
1447 the current working directory of that shortcut or script in a sub-directory |
|
1448 called "workspace". For Windows users, this is specified by the |
|
1449 "Start in:" argument in your shortcut properties.</li> |
|
1450 <li>Copy this workspace directory to a new, empty location outside of any |
|
1451 Eclipse install directory.</li> |
|
1452 <li>Install the new version of Eclipse in a new location, separate from any |
|
1453 old version of Eclipse.</li> |
|
1454 <li>If you had installed additional features and plug-ins into your old |
|
1455 Eclipse, you should re-install them in the new Eclipse.</li> |
|
1456 <li>Start this new version of Eclipse and select |
|
1457 this location using the workspace chooser dialog at startup (or use "<code>-data</code>" |
|
1458 command line argument to pre-select the workspace location).</li> |
|
1459 </ol> |
|
1460 <h3>Users who do use "-data"</h3> |
|
1461 <p>If you were previously using the "<code>-data</code>" argument to |
|
1462 start Eclipse, your upgrade path is much easier:</p> |
|
1463 |
|
1464 <ol> |
|
1465 <li>Optionally copy your workspace directory to a new, empty location outside of any |
|
1466 Eclipse install directory as a backup.</li> |
|
1467 <li>Install the new version of Eclipse in a new location, separate from any |
|
1468 old versions of Eclipse.</li> |
|
1469 <li>If you had installed additional features and plug-ins into your old |
|
1470 Eclipse, you should re-install them in the new Eclipse.</li> |
|
1471 <li>Start this new version of Eclipse and select this location using the workspace chooser dialog at |
|
1472 startup (or use "<code>-data</code>" |
|
1473 command line argument to pre-select the workspace location).</li> |
|
1474 </ol> |
|
1475 <p><i>Note:</i> Copying your workspace is recommended because, |
|
1476 after you've upgraded your workspace, you won't be able to use it |
|
1477 again with an older version of Eclipse. If you ever want to go "back in |
|
1478 time" to an earlier release, you will need that backup.</p> |
|
1479 |
|
1480 |
|
1481 <h2>6. <a name="Interoperability with Previous Releases">Interoperability with |
|
1482 Previous Releases</a></h2> |
|
1483 <h3>6.1 Interoperability of Release 3.5 with previous releases</h3> |
|
1484 <h4>Sharing projects between heterogeneous Eclipse 3.5 and 3.4</h4> |
|
1485 <p>Special care is required when a project in a team repository is being loaded |
|
1486 and operated on by developers using Eclipse-based products based on different |
|
1487 feature or plug-in versions. The general problem is that the existence, |
|
1488 contents, and interpretation of metadata files in the workspaces may be specific |
|
1489 to a particular feature or plug-in version, and differ between versions. The |
|
1490 workspace compatibility guarantees only cover cases where all developers upgrade |
|
1491 their Eclipse workspaces in lock step. In those cases there should be no problem |
|
1492 with shared metadata. However, when some developers are working in Eclipse 3.5 |
|
1493 while others are working in Eclipse 3.4, there are no such guarantees. |
|
1494 This section provides advice for what to do and not to do. It addresses the |
|
1495 specific issues with the Eclipse SDK.</p> |
|
1496 |
|
1497 <p>The typical failure mode is noticed by the 3.5 user. 3.5 metadata is lost |
|
1498 when a 3.4 user saves changes and then commits the updated metadata files to the |
|
1499 repository. Here's how things typically go awry:</p> |
|
1500 <ul> |
|
1501 <li>A user working in Eclipse 3.5 creates or modifies a project in a way that |
|
1502 results in changes to a shared metadata file that rely on 3.5-specific |
|
1503 information. The user then commits the updated project files, including the |
|
1504 shared metadata file, to the shared repository.</li> |
|
1505 <li>Another user working in Eclipse 3.4 shares this project from the same |
|
1506 repository. The 3.5-specific information in the shared metadata file is not |
|
1507 understood by Eclipse 3.4, and is generally discarded or ignored without |
|
1508 warning. The user modifies the project in a way that results in changes to |
|
1509 the shared metadata file, causing the shared metadata file to be rewritten |
|
1510 without any of the 3.5-specific information. The user commits the updated |
|
1511 project files, including the shared metadata file, to the shared repository. |
|
1512 The user is generally unaware that shared information has just been lost as |
|
1513 a result of their actions.</li> |
|
1514 <li>A user working in Eclipse 3.5 picks up the changes to a project from the |
|
1515 shared repository, including the updated shared metadata file. The user may |
|
1516 be unaware that they have just taken a retrograde step until later when |
|
1517 things start to malfunction.</li> |
|
1518 </ul> |
|
1519 <p>Here are some things to watch out for when sharing projects between |
|
1520 Eclipse 3.5 and earlier 3.x releases:</p> |
|
1521 <ul> |
|
1522 <li><b>Linked resources in the .project file</b> - |
|
1523 Eclipse 3.5 supports creating linked resources at arbitrary depth within a project, |
|
1524 and supports creating linked resources referring to other file systems. Neither of |
|
1525 these scenarios are supported in Eclipse 3.1 or earlier. If such linked resources |
|
1526 are created in 3.5, and the project is subsequently loaded into an Eclipse 3.1 |
|
1527 or earlier workspace, these links will not be recognized. Recommendation: |
|
1528 avoid creating links at arbitrary depth or to other file systems where project |
|
1529 compatibility with Eclipse 3.1 or earlier is required.</li> |
|
1530 </ul> |
|
1531 <h4>Using Eclipse 3.5 to develop plug-ins that work in Eclipse 3.4</h4> |
|
1532 <p>It is also possible (and reasonable) to use Eclipse 3.5 to develop a plug-in |
|
1533 intended to work in Eclipse 3.4 or earlier. Use the <b>Plug-in Development > |
|
1534 Target Platform </b>preference page to locate non-workspace plug-ins in an Eclipse |
|
1535 3.4 install. This ensures that the code for your plug-in is being compiled and |
|
1536 tested against Eclipse 3.4 APIs, extension points, and plug-ins. (The above |
|
1537 list of concerns do not apply since they affect the layout and interpretation |
|
1538 of files in the plug-in <i>project</i> but none affect the actual deployed form |
|
1539 of the plug-in.)</p> |
|
1540 |
|
1541 <hr> |
|
1542 <p>Sun, Solaris, Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. |
|
1543 in the United States, other countries, or both.</p> |
|
1544 <p>IBM is a trademark of International Business Machines Corporation in the |
|
1545 United States, other countries, or both.</p> |
|
1546 <p>Microsoft, Windows, Windows NT, Vista, and the Windows logo are trademarks of |
|
1547 Microsoft Corporation in the United States, other countries, or both.</p> |
|
1548 <p>Apple and Mac OS are trademarks of Apple Computer, Inc., registered in the |
|
1549 U.S. and other countries.</p> |
|
1550 <p>QNX, Neutrino, and Photon are trademarks or registered trademarks of QNX |
|
1551 Software Systems Ltd.</p> |
|
1552 <p>Other company, product, and service names may be trademarks or service marks |
|
1553 of others.</p> |
|
1554 <p>(c) Copyright IBM Corp. and others 2009</p> |
|
1555 |
|
1556 <h2><a name="Appendix1">Appendix 1: Execution Environment by Bundle</a></h2> |
|
1557 |
|
1558 <p>In the table below, the "3.5 minimum execution environment" |
|
1559 column indicates the minimum Java class library requirements of each bundle |
|
1560 for the 3.5 release, where the value is one of:</p> |
|
1561 <table border="0" width="90%"> |
|
1562 <tbody> |
|
1563 <tr> |
|
1564 <td align="center"><b>Entry</b></td> |
|
1565 <td align="left"><b>Meaning</b></td> |
|
1566 </tr> |
|
1567 <tr> |
|
1568 <td width="9%"> |
|
1569 <div align="center"><strong>M1.1</strong></div> |
|
1570 </td> |
|
1571 <td width="91%">OSGi Minimum Execution Environment 1.1 - This is a |
|
1572 subset of the J2ME Foundation class libraries defined by OSGi to |
|
1573 be the base for framework implementations. See the OSGi |
|
1574 specification for more details.</td> |
|
1575 </tr> |
|
1576 <tr> |
|
1577 <td><div align="center"><strong>F1.0</strong></div></td> |
|
1578 <td>J2ME Foundation 1.0 - indicates that the bundle can only be run on |
|
1579 Foundation 1.0 or greater. Note that with the exception of some MicroEdition |
|
1580 IO classes, Foundation 1.0 is a subset of J2SE 1.3.</td> |
|
1581 </tr> |
|
1582 <tr> |
|
1583 <td><div align="center"><strong>F1.1</strong></div></td> |
|
1584 <td>J2ME Foundation 1.1 - indicates that the bundle can only be run on |
|
1585 Foundation 1.1 or greater. Note that with the exception of some MicroEdition |
|
1586 IO classes, Foundation 1.1 is a subset of J2SE 1.4.</td> |
|
1587 </tr> |
|
1588 <tr> |
|
1589 <td><div align="center"><strong>1.3</strong></div></td> |
|
1590 <td>J2SE 1.3 - indicates that the bundle can only be run on JSE 1.3 or |
|
1591 greater.</td> |
|
1592 </tr> |
|
1593 |
|
1594 <tr> |
|
1595 <td><div align="center"><strong>1.4</strong></div></td> |
|
1596 <td>J2SE 1.4 - indicates that the bundle can only be run on JSE 1.4 or |
|
1597 greater.</td> |
|
1598 </tr> |
|
1599 <tr> |
|
1600 <td><div align="center"><strong>1.5</strong></div></td> |
|
1601 <td>Java SE 5 - indicates that the bundle can only be run on Java SE 5 or |
|
1602 greater.</td> |
|
1603 |
|
1604 </tr> |
|
1605 <tr> |
|
1606 <td><div align="center"><strong>1.6</strong></div></td> |
|
1607 <td>Java SE 6 - indicates that the bundle can only be run on Java SE 6 or |
|
1608 greater.</td> |
|
1609 </tr> |
|
1610 <tr> |
|
1611 <td align="center"><b>n/a</b></td> |
|
1612 <td>Not applicable. For example the bundle does not contain Java code.</td> |
|
1613 </tr> |
|
1614 </tbody> |
|
1615 </table> |
|
1616 <br> |
|
1617 <b>Table of minimum execution environments by bundle.</b><br> |
|
1618 <table border="1"> |
|
1619 <tbody> |
|
1620 <tr> |
|
1621 <td width="290"><strong>Bundle</strong></td> |
|
1622 <td width="60"><div align="center"> |
|
1623 <p align="center"><b>3.5<br> |
|
1624 minimum<br> |
|
1625 execution<br> |
|
1626 environment </b></p> |
|
1627 </div></td> |
|
1628 </tr> |
|
1629 <tr> |
|
1630 <td>aa.compute.bundle.ee</td> |
|
1631 <td><div align="center">1.5</div></td> |
|
1632 </tr> |
|
1633 <tr> |
|
1634 <td>com.ibm.icu</td> |
|
1635 <td><div align="center">F1.0</div></td> |
|
1636 </tr> |
|
1637 <tr> |
|
1638 <td>com.jcraft.jsch</td> |
|
1639 <td><div align="center">1.4</div></td> |
|
1640 </tr> |
|
1641 <tr> |
|
1642 <td>javax.servlet</td> |
|
1643 <td><div align="center">F1.1</div></td> |
|
1644 </tr> |
|
1645 <tr> |
|
1646 <td>javax.servlet.jsp</td> |
|
1647 <td><div align="center">F1.0</div></td> |
|
1648 </tr> |
|
1649 <tr> |
|
1650 <td>org.apache.ant</td> |
|
1651 <td><div align="center">J2SE-1.2</div></td> |
|
1652 </tr> |
|
1653 <tr> |
|
1654 <td>org.apache.commons.codec</td> |
|
1655 <td><div align="center">not specified</div></td> |
|
1656 </tr> |
|
1657 <tr> |
|
1658 <td>org.apache.commons.el</td> |
|
1659 <td><div align="center">F1.0</div></td> |
|
1660 </tr> |
|
1661 <tr> |
|
1662 <td>org.apache.commons.httpclient</td> |
|
1663 <td><div align="center">F1.0</div></td> |
|
1664 </tr> |
|
1665 <tr> |
|
1666 <td>org.apache.commons.logging</td> |
|
1667 <td><div align="center">F1.0</div></td> |
|
1668 </tr> |
|
1669 <tr> |
|
1670 <td>org.apache.jasper</td> |
|
1671 <td><div align="center">F1.0</div></td> |
|
1672 </tr> |
|
1673 <tr> |
|
1674 <td>org.apache.lucene</td> |
|
1675 <td><div align="center">not specified</div></td> |
|
1676 </tr> |
|
1677 <tr> |
|
1678 <td>org.apache.lucene.analysis</td> |
|
1679 <td><div align="center">not specified</div></td> |
|
1680 </tr> |
|
1681 <tr> |
|
1682 <td>org.eclipse.ant.core</td> |
|
1683 <td><div align="center">1.4</div></td> |
|
1684 </tr> |
|
1685 <tr> |
|
1686 <td>org.eclipse.ant.ui</td> |
|
1687 <td><div align="center">1.4</div></td> |
|
1688 </tr> |
|
1689 <tr> |
|
1690 <td>org.eclipse.compare</td> |
|
1691 <td><div align="center">1.4</div></td> |
|
1692 </tr> |
|
1693 <tr> |
|
1694 <td>org.eclipse.compare.core</td> |
|
1695 <td><div align="center">1.4</div></td> |
|
1696 </tr> |
|
1697 <tr> |
|
1698 <td>org.eclipse.compare.win32</td> |
|
1699 <td><div align="center">1.4</div></td> |
|
1700 </tr> |
|
1701 <tr> |
|
1702 <td>org.eclipse.core.boot</td> |
|
1703 <td><div align="center">F1.0</div></td> |
|
1704 </tr> |
|
1705 <tr> |
|
1706 <td>org.eclipse.core.commands</td> |
|
1707 <td><div align="center">F1.0</div></td> |
|
1708 </tr> |
|
1709 <tr> |
|
1710 <td>org.eclipse.core.contenttype</td> |
|
1711 <td><div align="center">F1.0</div></td> |
|
1712 </tr> |
|
1713 <tr> |
|
1714 <td>org.eclipse.core.databinding</td> |
|
1715 <td><div align="center">F1.1</div></td> |
|
1716 </tr> |
|
1717 <tr> |
|
1718 <td>org.eclipse.core.databinding.beans</td> |
|
1719 <td><div align="center">1.4</div></td> |
|
1720 </tr> |
|
1721 <tr> |
|
1722 <td>org.eclipse.core.databinding.observable</td> |
|
1723 <td><div align="center">F1.1</div></td> |
|
1724 </tr> |
|
1725 <tr> |
|
1726 <td>org.eclipse.core.databinding.property</td> |
|
1727 <td><div align="center">F1.1</div></td> |
|
1728 </tr> |
|
1729 <tr> |
|
1730 <td>org.eclipse.core.expressions</td> |
|
1731 <td><div align="center">F1.0</div></td> |
|
1732 </tr> |
|
1733 <tr> |
|
1734 <td>org.eclipse.core.filebuffers</td> |
|
1735 <td><div align="center">1.4</div></td> |
|
1736 </tr> |
|
1737 <tr> |
|
1738 <td>org.eclipse.core.filesystem</td> |
|
1739 <td><div align="center">1.4</div></td> |
|
1740 </tr> |
|
1741 <tr> |
|
1742 <td>org.eclipse.core.filesystem.win32.x86</td> |
|
1743 <td><div align="center">not specified</div></td> |
|
1744 </tr> |
|
1745 <tr> |
|
1746 <td>org.eclipse.core.jobs</td> |
|
1747 <td><div align="center">F1.0</div></td> |
|
1748 </tr> |
|
1749 <tr> |
|
1750 <td>org.eclipse.core.net</td> |
|
1751 <td><div align="center">F1.1</div></td> |
|
1752 </tr> |
|
1753 <tr> |
|
1754 <td>org.eclipse.core.net.win32.x86</td> |
|
1755 <td><div align="center">1.4</div></td> |
|
1756 </tr> |
|
1757 <tr> |
|
1758 <td>org.eclipse.core.resources</td> |
|
1759 <td><div align="center">1.4</div></td> |
|
1760 </tr> |
|
1761 <tr> |
|
1762 <td>org.eclipse.core.resources.compatibility</td> |
|
1763 <td><div align="center">1.4</div></td> |
|
1764 </tr> |
|
1765 <tr> |
|
1766 <td>org.eclipse.core.resources.win32.x86</td> |
|
1767 <td><div align="center">not specified</div></td> |
|
1768 </tr> |
|
1769 <tr> |
|
1770 <td>org.eclipse.core.runtime</td> |
|
1771 <td><div align="center">F1.0</div></td> |
|
1772 </tr> |
|
1773 <tr> |
|
1774 <td>org.eclipse.core.runtime.compatibility</td> |
|
1775 <td><div align="center">F1.0</div></td> |
|
1776 </tr> |
|
1777 <tr> |
|
1778 <td>org.eclipse.core.runtime.compatibility.auth</td> |
|
1779 <td><div align="center">F1.0</div></td> |
|
1780 </tr> |
|
1781 <tr> |
|
1782 <td>org.eclipse.core.runtime.compatibility.registry</td> |
|
1783 <td><div align="center">F1.0</div></td> |
|
1784 </tr> |
|
1785 <tr> |
|
1786 <td>org.eclipse.core.variables</td> |
|
1787 <td><div align="center">1.4</div></td> |
|
1788 </tr> |
|
1789 <tr> |
|
1790 <td>org.eclipse.cvs</td> |
|
1791 <td><div align="center">not specified</div></td> |
|
1792 </tr> |
|
1793 <tr> |
|
1794 <td>org.eclipse.debug.core</td> |
|
1795 <td><div align="center">1.4</div></td> |
|
1796 </tr> |
|
1797 <tr> |
|
1798 <td>org.eclipse.debug.ui</td> |
|
1799 <td><div align="center">1.4</div></td> |
|
1800 </tr> |
|
1801 <tr> |
|
1802 <td>org.eclipse.ecf</td> |
|
1803 <td><div align="center">F1.1</div></td> |
|
1804 </tr> |
|
1805 <tr> |
|
1806 <td>org.eclipse.ecf.filetransfer</td> |
|
1807 <td><div align="center">F1.0</div></td> |
|
1808 </tr> |
|
1809 <tr> |
|
1810 <td>org.eclipse.ecf.identity</td> |
|
1811 <td><div align="center">F1.1</div></td> |
|
1812 </tr> |
|
1813 <tr> |
|
1814 <td>org.eclipse.ecf.provider.filetransfer</td> |
|
1815 <td><div align="center">F1.1</div></td> |
|
1816 </tr> |
|
1817 <tr> |
|
1818 <td>org.eclipse.ecf.provider.filetransfer.httpclient</td> |
|
1819 <td><div align="center">F1.1</div></td> |
|
1820 </tr> |
|
1821 <tr> |
|
1822 <td>org.eclipse.ecf.provider.filetransfer.httpclient.ssl</td> |
|
1823 <td><div align="center">F1.1</div></td> |
|
1824 </tr> |
|
1825 <tr> |
|
1826 <td>org.eclipse.ecf.provider.filetransfer.ssl</td> |
|
1827 <td><div align="center">1.4</div></td> |
|
1828 </tr> |
|
1829 <tr> |
|
1830 <td>org.eclipse.ecf.ssl</td> |
|
1831 <td><div align="center">1.4</div></td> |
|
1832 </tr> |
|
1833 <tr> |
|
1834 <td>org.eclipse.equinox.app</td> |
|
1835 <td><div align="center">M1.2</div></td> |
|
1836 </tr> |
|
1837 <tr> |
|
1838 <td>org.eclipse.equinox.common</td> |
|
1839 <td><div align="center">F1.1</div></td> |
|
1840 </tr> |
|
1841 <tr> |
|
1842 <td>org.eclipse.equinox.concurrent</td> |
|
1843 <td><div align="center">F1.0</div></td> |
|
1844 </tr> |
|
1845 <tr> |
|
1846 <td>org.eclipse.equinox.ds</td> |
|
1847 <td><div align="center">M1.2</div></td> |
|
1848 </tr> |
|
1849 <tr> |
|
1850 <td>org.eclipse.equinox.frameworkadmin</td> |
|
1851 <td><div align="center">F1.1</div></td> |
|
1852 </tr> |
|
1853 <tr> |
|
1854 <td>org.eclipse.equinox.frameworkadmin.equinox</td> |
|
1855 <td><div align="center">F1.1</div></td> |
|
1856 </tr> |
|
1857 <tr> |
|
1858 <td>org.eclipse.equinox.http.jetty</td> |
|
1859 <td><div align="center">1.4</div></td> |
|
1860 </tr> |
|
1861 <tr> |
|
1862 <td>org.eclipse.equinox.http.registry</td> |
|
1863 <td><div align="center">F1.0</div></td> |
|
1864 </tr> |
|
1865 <tr> |
|
1866 <td>org.eclipse.equinox.http.servlet</td> |
|
1867 <td><div align="center">F1.0</div></td> |
|
1868 </tr> |
|
1869 <tr> |
|
1870 <td>org.eclipse.equinox.jsp.jasper</td> |
|
1871 <td><div align="center">F1.0</div></td> |
|
1872 </tr> |
|
1873 <tr> |
|
1874 <td>org.eclipse.equinox.jsp.jasper.registry</td> |
|
1875 <td><div align="center">F1.0</div></td> |
|
1876 </tr> |
|
1877 <tr> |
|
1878 <td>org.eclipse.equinox.launcher</td> |
|
1879 <td><div align="center">F1.0</div></td> |
|
1880 </tr> |
|
1881 <tr> |
|
1882 <td>org.eclipse.equinox.launcher.win32.win32.x86</td> |
|
1883 <td><div align="center">not specified</div></td> |
|
1884 </tr> |
|
1885 <tr> |
|
1886 <td>org.eclipse.equinox.p2.artifact.repository</td> |
|
1887 <td><div align="center">F1.1</div></td> |
|
1888 </tr> |
|
1889 <tr> |
|
1890 <td>org.eclipse.equinox.p2.console</td> |
|
1891 <td><div align="center">F1.1</div></td> |
|
1892 </tr> |
|
1893 <tr> |
|
1894 <td>org.eclipse.equinox.p2.core</td> |
|
1895 <td><div align="center">F1.1</div></td> |
|
1896 </tr> |
|
1897 <tr> |
|
1898 <td>org.eclipse.equinox.p2.director</td> |
|
1899 <td><div align="center">F1.1</div></td> |
|
1900 </tr> |
|
1901 <tr> |
|
1902 <td>org.eclipse.equinox.p2.director.app</td> |
|
1903 <td><div align="center">F1.1</div></td> |
|
1904 </tr> |
|
1905 <tr> |
|
1906 <td>org.eclipse.equinox.p2.directorywatcher</td> |
|
1907 <td><div align="center">F1.1</div></td> |
|
1908 </tr> |
|
1909 <tr> |
|
1910 <td>org.eclipse.equinox.p2.engine</td> |
|
1911 <td><div align="center">F1.1</div></td> |
|
1912 </tr> |
|
1913 <tr> |
|
1914 <td>org.eclipse.equinox.p2.exemplarysetup</td> |
|
1915 <td><div align="center">F1.1</div></td> |
|
1916 </tr> |
|
1917 <tr> |
|
1918 <td>org.eclipse.equinox.p2.extensionlocation</td> |
|
1919 <td><div align="center">F1.1</div></td> |
|
1920 </tr> |
|
1921 <tr> |
|
1922 <td>org.eclipse.equinox.p2.garbagecollector</td> |
|
1923 <td><div align="center">F1.1</div></td> |
|
1924 </tr> |
|
1925 <tr> |
|
1926 <td>org.eclipse.equinox.p2.jarprocessor</td> |
|
1927 <td><div align="center">F1.1</div></td> |
|
1928 </tr> |
|
1929 <tr> |
|
1930 <td>org.eclipse.equinox.p2.metadata</td> |
|
1931 <td><div align="center">F1.1</div></td> |
|
1932 </tr> |
|
1933 <tr> |
|
1934 <td>org.eclipse.equinox.p2.metadata.generator</td> |
|
1935 <td><div align="center">1.4</div></td> |
|
1936 </tr> |
|
1937 <tr> |
|
1938 <td>org.eclipse.equinox.p2.metadata.repository</td> |
|
1939 <td><div align="center">F1.1</div></td> |
|
1940 </tr> |
|
1941 <tr> |
|
1942 <td>org.eclipse.equinox.p2.publisher</td> |
|
1943 <td><div align="center">F1.1</div></td> |
|
1944 </tr> |
|
1945 <tr> |
|
1946 <td>org.eclipse.equinox.p2.reconciler.dropins</td> |
|
1947 <td><div align="center">F1.1</div></td> |
|
1948 </tr> |
|
1949 <tr> |
|
1950 <td>org.eclipse.equinox.p2.repository</td> |
|
1951 <td><div align="center">F1.1</div></td> |
|
1952 </tr> |
|
1953 <tr> |
|
1954 <td>org.eclipse.equinox.p2.repository.tools</td> |
|
1955 <td><div align="center">F1.1</div></td> |
|
1956 </tr> |
|
1957 <tr> |
|
1958 <td>org.eclipse.equinox.p2.touchpoint.eclipse</td> |
|
1959 <td><div align="center">F1.1</div></td> |
|
1960 </tr> |
|
1961 <tr> |
|
1962 <td>org.eclipse.equinox.p2.touchpoint.natives</td> |
|
1963 <td><div align="center">F1.1</div></td> |
|
1964 </tr> |
|
1965 <tr> |
|
1966 <td>org.eclipse.equinox.p2.ui</td> |
|
1967 <td><div align="center">F1.1</div></td> |
|
1968 </tr> |
|
1969 <tr> |
|
1970 <td>org.eclipse.equinox.p2.ui.sdk</td> |
|
1971 <td><div align="center">F1.1</div></td> |
|
1972 </tr> |
|
1973 <tr> |
|
1974 <td>org.eclipse.equinox.p2.ui.sdk.scheduler</td> |
|
1975 <td><div align="center">F1.1</div></td> |
|
1976 </tr> |
|
1977 <tr> |
|
1978 <td>org.eclipse.equinox.p2.updatechecker</td> |
|
1979 <td><div align="center">F1.1</div></td> |
|
1980 </tr> |
|
1981 <tr> |
|
1982 <td>org.eclipse.equinox.p2.updatesite</td> |
|
1983 <td><div align="center">F1.1</div></td> |
|
1984 </tr> |
|
1985 <tr> |
|
1986 <td>org.eclipse.equinox.preferences</td> |
|
1987 <td><div align="center">F1.1</div></td> |
|
1988 </tr> |
|
1989 <tr> |
|
1990 <td>org.eclipse.equinox.registry</td> |
|
1991 <td><div align="center">F1.0</div></td> |
|
1992 </tr> |
|
1993 <tr> |
|
1994 <td>org.eclipse.equinox.security</td> |
|
1995 <td><div align="center">1.4</div></td> |
|
1996 </tr> |
|
1997 <tr> |
|
1998 <td>org.eclipse.equinox.security.ui</td> |
|
1999 <td><div align="center">1.4</div></td> |
|
2000 </tr> |
|
2001 <tr> |
|
2002 <td>org.eclipse.equinox.security.win32.x86</td> |
|
2003 <td><div align="center">1.4</div></td> |
|
2004 </tr> |
|
2005 <tr> |
|
2006 <td>org.eclipse.equinox.simpleconfigurator</td> |
|
2007 <td><div align="center">F1.1</div></td> |
|
2008 </tr> |
|
2009 <tr> |
|
2010 <td>org.eclipse.equinox.simpleconfigurator.manipulator</td> |
|
2011 <td><div align="center">F1.1</div></td> |
|
2012 </tr> |
|
2013 <tr> |
|
2014 <td>org.eclipse.equinox.util</td> |
|
2015 <td><div align="center">M1.1</div></td> |
|
2016 </tr> |
|
2017 <tr> |
|
2018 <td>org.eclipse.help</td> |
|
2019 <td><div align="center">F1.0</div></td> |
|
2020 </tr> |
|
2021 <tr> |
|
2022 <td>org.eclipse.help.appserver</td> |
|
2023 <td><div align="center">F1.0</div></td> |
|
2024 </tr> |
|
2025 <tr> |
|
2026 <td>org.eclipse.help.base</td> |
|
2027 <td><div align="center">1.4</div></td> |
|
2028 </tr> |
|
2029 <tr> |
|
2030 <td>org.eclipse.help.ui</td> |
|
2031 <td><div align="center">1.4</div></td> |
|
2032 </tr> |
|
2033 <tr> |
|
2034 <td>org.eclipse.help.webapp</td> |
|
2035 <td><div align="center">1.4</div></td> |
|
2036 </tr> |
|
2037 <tr> |
|
2038 <td>org.eclipse.jdt</td> |
|
2039 <td><div align="center">not specified</div></td> |
|
2040 </tr> |
|
2041 <tr> |
|
2042 <td>org.eclipse.jdt.apt.core</td> |
|
2043 <td><div align="center">1.5</div></td> |
|
2044 </tr> |
|
2045 <tr> |
|
2046 <td>org.eclipse.jdt.apt.pluggable.core</td> |
|
2047 <td><div align="center">1.6</div></td> |
|
2048 </tr> |
|
2049 <tr> |
|
2050 <td>org.eclipse.jdt.apt.ui</td> |
|
2051 <td><div align="center">1.5</div></td> |
|
2052 </tr> |
|
2053 <tr> |
|
2054 <td>org.eclipse.jdt.compiler.apt</td> |
|
2055 <td><div align="center">1.6</div></td> |
|
2056 </tr> |
|
2057 <tr> |
|
2058 <td>org.eclipse.jdt.compiler.tool</td> |
|
2059 <td><div align="center">1.6</div></td> |
|
2060 </tr> |
|
2061 <tr> |
|
2062 <td>org.eclipse.jdt.core</td> |
|
2063 <td><div align="center">1.4</div></td> |
|
2064 </tr> |
|
2065 <tr> |
|
2066 <td>org.eclipse.jdt.core.manipulation</td> |
|
2067 <td><div align="center">1.4</div></td> |
|
2068 </tr> |
|
2069 <tr> |
|
2070 <td>org.eclipse.jdt.debug</td> |
|
2071 <td><div align="center">1.4</div></td> |
|
2072 </tr> |
|
2073 <tr> |
|
2074 <td>org.eclipse.jdt.debug.ui</td> |
|
2075 <td><div align="center">1.4</div></td> |
|
2076 </tr> |
|
2077 <tr> |
|
2078 <td>org.eclipse.jdt.doc.isv</td> |
|
2079 <td><div align="center">not specified</div></td> |
|
2080 </tr> |
|
2081 <tr> |
|
2082 <td>org.eclipse.jdt.doc.user</td> |
|
2083 <td><div align="center">not specified</div></td> |
|
2084 </tr> |
|
2085 <tr> |
|
2086 <td>org.eclipse.jdt.junit</td> |
|
2087 <td><div align="center">1.4</div></td> |
|
2088 </tr> |
|
2089 <tr> |
|
2090 <td>org.eclipse.jdt.junit.runtime</td> |
|
2091 <td><div align="center">1.3</div></td> |
|
2092 </tr> |
|
2093 <tr> |
|
2094 <td>org.eclipse.jdt.junit4.runtime</td> |
|
2095 <td><div align="center">1.5</div></td> |
|
2096 </tr> |
|
2097 <tr> |
|
2098 <td>org.eclipse.jdt.launching</td> |
|
2099 <td><div align="center">1.4</div></td> |
|
2100 </tr> |
|
2101 <tr> |
|
2102 <td>org.eclipse.jdt.ui</td> |
|
2103 <td><div align="center">1.4</div></td> |
|
2104 </tr> |
|
2105 <tr> |
|
2106 <td>org.eclipse.jface</td> |
|
2107 <td><div align="center">F1.1</div></td> |
|
2108 </tr> |
|
2109 <tr> |
|
2110 <td>org.eclipse.jface.databinding</td> |
|
2111 <td><div align="center">F1.0</div></td> |
|
2112 </tr> |
|
2113 <tr> |
|
2114 <td>org.eclipse.jface.text</td> |
|
2115 <td><div align="center">1.4</div></td> |
|
2116 </tr> |
|
2117 <tr> |
|
2118 <td>org.eclipse.jsch.core</td> |
|
2119 <td><div align="center">1.4</div></td> |
|
2120 </tr> |
|
2121 <tr> |
|
2122 <td>org.eclipse.jsch.ui</td> |
|
2123 <td><div align="center">1.4</div></td> |
|
2124 </tr> |
|
2125 <tr> |
|
2126 <td>org.eclipse.ltk.core.refactoring</td> |
|
2127 <td><div align="center">1.4</div></td> |
|
2128 </tr> |
|
2129 <tr> |
|
2130 <td>org.eclipse.ltk.ui.refactoring</td> |
|
2131 <td><div align="center">1.4</div></td> |
|
2132 </tr> |
|
2133 <tr> |
|
2134 <td>org.eclipse.osgi</td> |
|
2135 <td><div align="center">M1.2</div></td> |
|
2136 </tr> |
|
2137 <tr> |
|
2138 <td>org.eclipse.osgi.services</td> |
|
2139 <td><div align="center">M1.2</div></td> |
|
2140 </tr> |
|
2141 <tr> |
|
2142 <td>org.eclipse.osgi.util</td> |
|
2143 <td><div align="center">M1.2</div></td> |
|
2144 </tr> |
|
2145 <tr> |
|
2146 <td>org.eclipse.pde</td> |
|
2147 <td><div align="center">1.4</div></td> |
|
2148 </tr> |
|
2149 <tr> |
|
2150 <td>org.eclipse.pde.api.tools</td> |
|
2151 <td><div align="center">1.4</div></td> |
|
2152 </tr> |
|
2153 <tr> |
|
2154 <td>org.eclipse.pde.api.tools.ui</td> |
|
2155 <td><div align="center">1.4</div></td> |
|
2156 </tr> |
|
2157 <tr> |
|
2158 <td>org.eclipse.pde.build</td> |
|
2159 <td><div align="center">1.4</div></td> |
|
2160 </tr> |
|
2161 <tr> |
|
2162 <td>org.eclipse.pde.core</td> |
|
2163 <td><div align="center">1.4</div></td> |
|
2164 </tr> |
|
2165 <tr> |
|
2166 <td>org.eclipse.pde.doc.user</td> |
|
2167 <td><div align="center">not specified</div></td> |
|
2168 </tr> |
|
2169 <tr> |
|
2170 <td>org.eclipse.pde.ds.core</td> |
|
2171 <td><div align="center">1.4</div></td> |
|
2172 </tr> |
|
2173 <tr> |
|
2174 <td>org.eclipse.pde.ds.ui</td> |
|
2175 <td><div align="center">1.4</div></td> |
|
2176 </tr> |
|
2177 <tr> |
|
2178 <td>org.eclipse.pde.junit.runtime</td> |
|
2179 <td><div align="center">1.4</div></td> |
|
2180 </tr> |
|
2181 <tr> |
|
2182 <td>org.eclipse.pde.runtime</td> |
|
2183 <td><div align="center">1.4</div></td> |
|
2184 </tr> |
|
2185 <tr> |
|
2186 <td>org.eclipse.pde.ua.core</td> |
|
2187 <td><div align="center">1.4</div></td> |
|
2188 </tr> |
|
2189 <tr> |
|
2190 <td>org.eclipse.pde.ua.ui</td> |
|
2191 <td><div align="center">1.4</div></td> |
|
2192 </tr> |
|
2193 <tr> |
|
2194 <td>org.eclipse.pde.ui</td> |
|
2195 <td><div align="center">1.4</div></td> |
|
2196 </tr> |
|
2197 <tr> |
|
2198 <td>org.eclipse.pde.ui.templates</td> |
|
2199 <td><div align="center">1.4</div></td> |
|
2200 </tr> |
|
2201 <tr> |
|
2202 <td>org.eclipse.platform</td> |
|
2203 <td><div align="center">F1.0</div></td> |
|
2204 </tr> |
|
2205 <tr> |
|
2206 <td>org.eclipse.platform.doc.isv</td> |
|
2207 <td><div align="center">not specified</div></td> |
|
2208 </tr> |
|
2209 <tr> |
|
2210 <td>org.eclipse.platform.doc.user</td> |
|
2211 <td><div align="center">not specified</div></td> |
|
2212 </tr> |
|
2213 <tr> |
|
2214 <td>org.eclipse.rcp</td> |
|
2215 <td><div align="center">not specified</div></td> |
|
2216 </tr> |
|
2217 <tr> |
|
2218 <td>org.eclipse.sdk</td> |
|
2219 <td><div align="center">not specified</div></td> |
|
2220 </tr> |
|
2221 <tr> |
|
2222 <td>org.eclipse.search</td> |
|
2223 <td><div align="center">1.4</div></td> |
|
2224 </tr> |
|
2225 <tr> |
|
2226 <td>org.eclipse.swt</td> |
|
2227 <td><div align="center">F1.0</div></td> |
|
2228 </tr> |
|
2229 <tr> |
|
2230 <td>org.eclipse.swt.win32.win32.x86</td> |
|
2231 <td><div align="center">F1.0</div></td> |
|
2232 </tr> |
|
2233 <tr> |
|
2234 <td>org.eclipse.team.core</td> |
|
2235 <td><div align="center">1.4</div></td> |
|
2236 </tr> |
|
2237 <tr> |
|
2238 <td>org.eclipse.team.cvs.core</td> |
|
2239 <td><div align="center">1.4</div></td> |
|
2240 </tr> |
|
2241 <tr> |
|
2242 <td>org.eclipse.team.cvs.ssh</td> |
|
2243 <td><div align="center">1.4</div></td> |
|
2244 </tr> |
|
2245 <tr> |
|
2246 <td>org.eclipse.team.cvs.ssh2</td> |
|
2247 <td><div align="center">1.4</div></td> |
|
2248 </tr> |
|
2249 <tr> |
|
2250 <td>org.eclipse.team.cvs.ui</td> |
|
2251 <td><div align="center">1.4</div></td> |
|
2252 </tr> |
|
2253 <tr> |
|
2254 <td>org.eclipse.team.ui</td> |
|
2255 <td><div align="center">1.4</div></td> |
|
2256 </tr> |
|
2257 <tr> |
|
2258 <td>org.eclipse.text</td> |
|
2259 <td><div align="center">1.4</div></td> |
|
2260 </tr> |
|
2261 <tr> |
|
2262 <td>org.eclipse.ui</td> |
|
2263 <td><div align="center">F1.0</div></td> |
|
2264 </tr> |
|
2265 <tr> |
|
2266 <td>org.eclipse.ui.browser</td> |
|
2267 <td><div align="center">1.4</div></td> |
|
2268 </tr> |
|
2269 <tr> |
|
2270 <td>org.eclipse.ui.cheatsheets</td> |
|
2271 <td><div align="center">1.4</div></td> |
|
2272 </tr> |
|
2273 <tr> |
|
2274 <td>org.eclipse.ui.console</td> |
|
2275 <td><div align="center">1.4</div></td> |
|
2276 </tr> |
|
2277 <tr> |
|
2278 <td>org.eclipse.ui.editors</td> |
|
2279 <td><div align="center">1.4</div></td> |
|
2280 </tr> |
|
2281 <tr> |
|
2282 <td>org.eclipse.ui.externaltools</td> |
|
2283 <td><div align="center">1.4</div></td> |
|
2284 </tr> |
|
2285 <tr> |
|
2286 <td>org.eclipse.ui.forms</td> |
|
2287 <td><div align="center">1.4</div></td> |
|
2288 </tr> |
|
2289 <tr> |
|
2290 <td>org.eclipse.ui.ide</td> |
|
2291 <td><div align="center">1.4</div></td> |
|
2292 </tr> |
|
2293 <tr> |
|
2294 <td>org.eclipse.ui.ide.application</td> |
|
2295 <td><div align="center">1.4</div></td> |
|
2296 </tr> |
|
2297 <tr> |
|
2298 <td>org.eclipse.ui.intro</td> |
|
2299 <td><div align="center">1.4</div></td> |
|
2300 </tr> |
|
2301 <tr> |
|
2302 <td>org.eclipse.ui.intro.universal</td> |
|
2303 <td><div align="center">1.4</div></td> |
|
2304 </tr> |
|
2305 <tr> |
|
2306 <td>org.eclipse.ui.navigator</td> |
|
2307 <td><div align="center">1.4</div></td> |
|
2308 </tr> |
|
2309 <tr> |
|
2310 <td>org.eclipse.ui.navigator.resources</td> |
|
2311 <td><div align="center">1.4</div></td> |
|
2312 </tr> |
|
2313 <tr> |
|
2314 <td>org.eclipse.ui.net</td> |
|
2315 <td><div align="center">F1.1</div></td> |
|
2316 </tr> |
|
2317 <tr> |
|
2318 <td>org.eclipse.ui.presentations.r21</td> |
|
2319 <td><div align="center">1.4</div></td> |
|
2320 </tr> |
|
2321 <tr> |
|
2322 <td>org.eclipse.ui.views</td> |
|
2323 <td><div align="center">1.4</div></td> |
|
2324 </tr> |
|
2325 <tr> |
|
2326 <td>org.eclipse.ui.views.log</td> |
|
2327 <td><div align="center">1.4</div></td> |
|
2328 </tr> |
|
2329 <tr> |
|
2330 <td>org.eclipse.ui.views.properties.tabbed</td> |
|
2331 <td><div align="center">F1.0</div></td> |
|
2332 </tr> |
|
2333 <tr> |
|
2334 <td>org.eclipse.ui.win32</td> |
|
2335 <td><div align="center">1.4</div></td> |
|
2336 </tr> |
|
2337 <tr> |
|
2338 <td>org.eclipse.ui.workbench</td> |
|
2339 <td><div align="center">F1.1</div></td> |
|
2340 </tr> |
|
2341 <tr> |
|
2342 <td>org.eclipse.ui.workbench.compatibility</td> |
|
2343 <td><div align="center">1.4</div></td> |
|
2344 </tr> |
|
2345 <tr> |
|
2346 <td>org.eclipse.ui.workbench.texteditor</td> |
|
2347 <td><div align="center">1.4</div></td> |
|
2348 </tr> |
|
2349 <tr> |
|
2350 <td>org.eclipse.update.configurator</td> |
|
2351 <td><div align="center">F1.0</div></td> |
|
2352 </tr> |
|
2353 <tr> |
|
2354 <td>org.eclipse.update.core</td> |
|
2355 <td><div align="center">F1.0</div></td> |
|
2356 </tr> |
|
2357 <tr> |
|
2358 <td>org.eclipse.update.core.win32</td> |
|
2359 <td><div align="center">not specified</div></td> |
|
2360 </tr> |
|
2361 <tr> |
|
2362 <td>org.eclipse.update.scheduler</td> |
|
2363 <td><div align="center">F1.0</div></td> |
|
2364 </tr> |
|
2365 <tr> |
|
2366 <td>org.eclipse.update.ui</td> |
|
2367 <td><div align="center">F1.0</div></td> |
|
2368 </tr> |
|
2369 <tr> |
|
2370 <td>org.hamcrest.core</td> |
|
2371 <td><div align="center">1.5</div></td> |
|
2372 </tr> |
|
2373 <tr> |
|
2374 <td>org.junit</td> |
|
2375 <td><div align="center">1.3</div></td> |
|
2376 </tr> |
|
2377 <tr> |
|
2378 <td>org.junit4</td> |
|
2379 <td><div align="center">1.5</div></td> |
|
2380 </tr> |
|
2381 <tr> |
|
2382 <td>org.mortbay.jetty.server</td> |
|
2383 <td><div align="center">1.4</div></td> |
|
2384 </tr> |
|
2385 <tr> |
|
2386 <td>org.mortbay.jetty.util</td> |
|
2387 <td><div align="center">1.4</div></td> |
|
2388 </tr> |
|
2389 <tr> |
|
2390 <td>org.objectweb.asm</td> |
|
2391 <td><div align="center">1.3</div></td> |
|
2392 </tr> |
|
2393 <tr> |
|
2394 <td>org.sat4j.core</td> |
|
2395 <td><div align="center">1.4</div></td> |
|
2396 </tr> |
|
2397 <tr> |
|
2398 <td>org.sat4j.pb</td> |
|
2399 <td><div align="center">1.4</div></td> |
|
2400 </tr> |
|
2401 </tbody> |
|
2402 </table> |
|
2403 |
|
2404 </body> |
|
2405 </html> |
|
2406 |