1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
4 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
5 <title>Eclipse Project Release Notes 4.2</title>
9 <h1>Eclipse Project Release Notes</h1>
11 Last revised June 8th, 2012</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>
15 <p align="left"><a href="#TargetOperatingEnvironments">1. Target Operating
17 <a href="#Compatibility">2. Compatibility with Previous
19 <a href="#KnownIssues">3. Known Issues</a><br/>
20 <a href="#RunningEclipse">4. Running Eclipse</a><br/>
21 <a href="#Upgrading">5. Upgrading a Workspace from a Previous Release</a><br/>
22 <a href="#InteroperabilityWithPreviousReleases">6. Interoperability with
23 Previous Releases</a><br/>
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.1, J2SE 1.4, Java 5, etc).</p>
35 <p>In general, the 4.2 release of the Eclipse Project is developed on
36 Java SE 6 VMs. As such, the Eclipse SDK as a whole is targeted at all modern, desktop Java VMs.
37 Most functionality is available for Java SE 6 level development everywhere, and extended development capabilities are made
38 available on the VMs that support them.</p>
39 <p><a href="#appendix">Appendix 1</a> contains a table that indicates the class
40 library level required for each bundle.</p>
41 <p>There are many different implementations of the Java Platform running atop
42 a variety of operating systems. We focus our testing on a handful of
43 popular combinations of operating system and Java Platform; these are our <em>reference
44 platforms</em>. Eclipse undoubtedly runs fine in many operating environments
45 beyond the reference platforms we test. However, since we do not systematically test
46 them we cannot vouch for them. Problems encountered when running Eclipse on a
47 non-reference platform that cannot be recreated on any reference platform will
48 be given lower priority than problems with running Eclipse on a reference platform.</p>
49 <p>Eclipse 4.2 is tested and validated on the following reference platforms
50 (this list is updated over the course of the release cycle):</p>
51 <style type="text/css">
56 border-collapse: separate;
63 background-color: #B9A9FF;
66 border-width: 1px 1px 1px 1px;
67 padding: 3px 3px 3px 3px;
68 border-style: inset inset inset inset;
69 border-color: gray gray gray gray;
71 table.platforms tr.c0 td {
72 background-color: #FDFDFD;
74 table.platforms tr.c1 td {
75 background-color: #F4EEFF;
79 <table class="platforms">
81 <th>Operating System</th>
85 <th>Windowing System</th>
87 <!-- ************ WINDOWS ************** -->
89 <td rowspan="4">Windows</td>
90 <td rowspan="2">7</td>
91 <td rowspan="1">x86 32-bit</td>
92 <td rowspan="4">Oracle Java 7 Update 2<br/>
93 Oracle Java 6 Update 27<br/>
96 <td rowspan="4">Win32</td>
99 <td rowspan="1">x86 64-bit</td>
102 <td rowspan="2">XP</td>
103 <td rowspan="1">x86 32-bit</td>
106 <td rowspan="1">x86 64-bit</td>
108 <!-- ************ RHEL ************** -->
110 <td rowspan="3">Red Hat Enterprise Linux</td>
111 <td rowspan="3">6</td>
112 <td rowspan="1">x86 32-bit</td>
114 Oracle Java 7 Update 2<br/>
115 Oracle Java 6 Update 27<br/>
118 <td rowspan="3">GTK</td>
121 <td rowspan="1">x86 64-bit</td>
124 <td rowspan="1">Power 64-bit</td>
125 <td>IBM Java 6 SR9</td>
127 <!-- ************ SLES ************** -->
129 <td rowspan="3">SUSE Linux Enterprise Server</td>
130 <td rowspan="3">11</td>
131 <td rowspan="1">x86 32-bit</td>
132 <td rowspan="2">Oracle Java 6 Update 27<br/>
135 <td rowspan="3">GTK</td>
138 <td rowspan="1">x86 64-bit</td>
141 <td rowspan="1">Power 64-bit</td>
142 <td>IBM Java 6 SR9</td>
144 <!-- ************ Ubuntu ************** -->
146 <td rowspan="2">Ubuntu Long Term Support</td>
147 <td rowspan="2">10.04</td>
148 <td rowspan="1">x86 32-bit</td>
149 <td rowspan="2">Oracle Java 6 Update 27<br/>
152 <td rowspan="2">GTK</td>
155 <td rowspan="1">x86 64-bit</td>
157 <!-- ************ Solaris ************** -->
159 <td rowspan="2">Oracle Solaris</td>
160 <td rowspan="2">11</td>
161 <td rowspan="1">x86 32-bit</td>
162 <td rowspan="2">Oracle Java 6 Update 27</td>
163 <td rowspan="2">GTK</td>
166 <td rowspan="1">SPARC 32-bit</td>
168 <!-- ************ HPUX ************** -->
170 <td rowspan="1">HP-UX</td>
171 <td rowspan="1">11i v3</td>
172 <td rowspan="1">ia64 32-bit</td>
173 <td rowspan="1">HP-UX Java 6 Update 10</td>
174 <td rowspan="1">GTK</td>
176 <!-- ************ AIX ************** -->
178 <td rowspan="1">IBM AIX</td>
179 <td rowspan="1">7.1</td>
180 <td rowspan="1">Power 64-bit</td>
181 <td rowspan="1">IBM Java 6 SR9</td>
182 <td rowspan="1">GTK</td>
184 <!-- ************ Mac ************** -->
186 <td rowspan="2">Apple Mac OS X</td>
187 <td rowspan="2">10.6</td>
188 <td rowspan="1">Universal 32-bit</td>
189 <td rowspan="2">Apple Java 10.6 Update 5</td>
190 <td rowspan="2">Cocoa</td>
193 <td rowspan="1">Universal 64-bit</td>
198 <p>As stated above, <i>we expect that Eclipse works fine on other current
199 Java VM and OS versions but we cannot flag these as reference platforms without
200 significant community support for testing them.</i></p>
202 <p>The Eclipse SDK is designed as the basis for internationalized products. The
203 user interface elements provided by the Eclipse SDK components, including dialogs
204 and error messages, are externalized. The English strings are provided as the
205 default resource bundles.</p>
206 <p>Latin-1, DBCS, and BiDi locales are supported by the Eclipse SDK on all reference platforms.</p>
207 <p>The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard,
208 on Windows, Linux and the Macintosh.</p>
209 <p>German and Japanese locales are tested.</p>
211 <h2>2. <a name="Compatibility"></a>Compatibility with Previous Releases</h2>
212 <h3>Compatibility of Release 4.2 with 3.8</h3>
213 <p>Eclipse 4.2 is compatible with Eclipse 3.8 (and all earlier 3.x versions).</p>
215 <p><strong>API Contract Compatibility:</strong> Eclipse SDK 4.2 is upwards
216 contract-compatible with Eclipse SDK 3.8 except in those areas noted in the
217 <a href="http://git.eclipse.org/c/platform/eclipse.platform.common.git/plain/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_2_porting_guide.html?h=R4_HEAD" target="_top">
218 <em>Eclipse 4.2 Plug-in Migration Guide</em>
219 </a>. Programs that use affected APIs and extension points will need to be ported
220 to Eclipse SDK 4.2 APIs. Downward contract compatibility
221 is not supported. There is no guarantee that compliance with Eclipse SDK 4.2
222 APIs would ensure compliance with Eclipse SDK 3.8 APIs. Refer to
223 <a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">
224 <em>Evolving Java-based APIs</em>
225 </a> for a discussion of the kinds of API changes that maintain contract compatibility.</p>
227 <p><strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 4.2 is upwards
228 binary-compatible with Eclipse SDK 3.8 except in those areas noted in the
229 <a href="http://git.eclipse.org/c/platform/eclipse.platform.common.git/plain/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_2_porting_guide.html?h=R4_HEAD" target="_top">
230 <em>Eclipse 4.2 Plug-in Migration Guide</em>
231 </a>. Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK
232 4.2 will not be usable in Eclipse SDK 3.8. Refer to
233 <a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">
234 <em>Evolving Java-based APIs</em>
235 </a> for a discussion of the kinds of API changes that maintain binary compatibility.</p>
237 <p><strong>Source Compatibility:</strong> Eclipse SDK 4.2 is upwards source-compatible
238 with Eclipse SDK 3.8 except in the areas noted in the
239 <a href="http://git.eclipse.org/c/platform/eclipse.platform.common.git/plain/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_2_porting_guide.html?h=R4_HEAD" target="_top">
240 <em>Eclipse 4.2 Plug-in Migration Guide</em>
241 </a>. This means that source files written
242 to use Eclipse SDK 3.8 APIs might successfully compile and run against Eclipse
243 SDK 4.2 APIs, although this is not guaranteed. Downward source compatibility
244 is not supported. If source files use new Eclipse SDK APIs, they will not be
245 usable with an earlier version of the Eclipse SDK. </p>
247 <p><strong>Workspace Compatibility:</strong> Eclipse SDK 4.2 is upwards
248 workspace-compatible with earlier 3.x and 4.x versions of the Eclipse SDK unless noted.
249 This means that workspaces and projects created with Eclipse SDK 4.1, 4.0, 3.8 .. 3.0 can be successfully
250 opened by Eclipse SDK 4.2 and upgraded to a 4.2 workspace. This includes both
251 hidden metadata, which is localized to a particular workspace, as well as metadata
252 files found within a workspace project (e.g., the .project file), which may
253 propagate between workspaces via file copying or team repositories. Individual
254 plug-ins developed for Eclipse SDK 4.2 should provide similar upwards compatibility
255 for their hidden and visible workspace metadata created by earlier versions;
256 4.2 plug-in developers are responsible for ensuring that their plug-ins recognize
257 metadata from earlier versions and process it appropriately. User
258 interface session state may be discarded when a workspace is upgraded. Downward
259 workspace compatibility is not supported. A workspace created (or opened) by
260 a product based on Eclipse 4.2 will be unusable with a product based on an earlier
261 version of Eclipse. Visible metadata files created (or overwritten) by Eclipse
262 4.2 will generally be unusable with earlier versions of Eclipse. </p>
264 <p><strong>Non-compliant usage of API's</strong>: All non-API methods and classes,
265 and certainly everything in a package with "internal" in its name or
266 x-internal in the bundle manifest entry,
267 are considered implementation details which may vary between operating environment
268 and are subject to change without notice. Client plug-ins that directly depend
269 on anything other than what is specified in the Eclipse SDK API are inherently
270 unsupportable and receive no guarantees about compatibility within a single
271 release much less with earlier releases. Refer to
272 <a href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">
273 <em>How to Use the Eclipse API</em>
274 </a> for information about how to write compliant plug-ins. </p>
276 <h2>3. <a name="KnownIssues"></a> Known Issues</h2>
278 <a href="#I-General">
279 3.1 General problems</a><br/>
280 <a href="#I-General-Startup">3.1.1 Startup</a><br/>
281 <a href="#I-General-GCJ">3.1.2 GCJ</a><br/>
282 <a href="#I-General-64bitJava">3.1.3 64-bit Java HotSpot(TM) VM</a><br/>
283 <a href="#I-Platform">3.2 Platform</a><br/>
284 <a href="#I-Platform-Core">3.2.1 Core</a><br/>
286 <a href="#I-Platform-Ant">3.2.2 Ant</a><br/>
287 <a href="#I-Platform-User-Assistance">3.2.3 User Assistance</a><br/>
288 <a href="#I-Platform-UI">3.2.4 UI</a><br/>
289 <a href="#I-Platform-Text">3.2.5 Text</a><br/>
290 <a href="#I-Platform-SWT">3.2.6 SWT</a><br/>
292 <a href="#I-Platform-Team-CVS">3.2.7 Team and CVS</a><br/>
293 <a href="#I-Platform-Install-Update">3.2.8 Install/Update</a><br/>
294 <a href="#I-Platform-Debug">3.2.9 Debug</a><br/>
295 <a href="#I-Platform-Compare">3.2.10 Compare</a><br/>
297 3.3 Java development tools (JDT)</a><br/>
299 3.4 Plug-in Development Environment (PDE)</a><br/>
302 <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>
304 <h3>3.1 <a name="I-General">General problems</a></h3>
306 <h3>3.1.1 <a name="I-General-Startup">General - Startup</a></h3>
307 <h4>Installation/Configuration issues that can cause Eclipse to fail start</h4>
308 <p>Here are some common problems that can cause Eclipse not to start:</p>
310 <li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 4.2 requires
311 at least a Java SE 6. Perhaps an older version of the VM is being found in
312 your path. To explicitly specify which VM to run with, use the Eclipse <tt>-vm</tt>
313 command-line argument. (See also the <a href="#RunningEclipse">Running Eclipse</a>
316 Running Eclipse on Gentoo Linux may result in the following error message:
317 <div style="margin-left: 40px;">
318 <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>
321 If this occurs, start Eclipse by specifying a -vm argument, either
322 specify the path to a java vm or use: <tt>eclipse -vm `java-config</tt>
323 --java` (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=176021">176021</a>)</li>
324 <li>Eclipse must be installed to a clean directory and not installed over top of
325 a previous installation. If you have done this then please re-install to a new
326 directory. If your workspace is in a child directory of your old installation
327 directory, then see the instructions below on "<a href="#upgrading">Upgrading Workspace from a
328 Previous Release"</a>.</li>
330 <li>Java sometimes has difficulty detecting whether a file system is writable. In
331 particular, the method java.io.File.canWrite() appears to return true in
332 unexpected cases (e.g., using Windows drive sharing where the share is a
333 read-only Samba drive). The Eclipse runtime generally needs a writable
334 configuration area and as a result of this problem, may erroneously detect the
335 current configuration location as writable. The net result is that Eclipse will
336 fail to start and depending on the circumstances, may fail to write a log file
337 with any details. To work around this, we suggest users experiencing this
338 problem set their configuration area explicitly using the <tt>-configuration</tt> command
339 line argument. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=67719">67719</a>)</li>
342 <h4><b>Invalid characters in install directory prevents Eclipse from starting</b></h4>
343 <p>Eclipse will fail to launch if installed in a directory whose path
344 contains certain invalid characters, including :%#<>"!. The
345 workaround is to install Eclipse in a directory whose path does not contain
346 invalid characters. (bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=3109">3109</a>
347 and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=17281">17281</a>)</p>
349 <h4>Hanging during class loading when out of permanent generation memory</h4>
351 The Sun VM may hang indefinitely during class loading if it runs out of permanent
352 generation memory. This will cause CPU usage to stay at 100% until the process
353 is ended. See the section <a href="#RunningEclipse">Running Eclipse</a> for details
354 on addressing this VM problem.
357 <h3>3.1.2 <a name="I-General-GCJ">General - GCJ</a></h3>
358 <p>GCJ is an effort by the GCC team to provide an open source Java compiler and
359 runtime environment to interpret Java bytecode. Unfortunately, the GCJ runtime
360 environment is not an environment that is often tested on by Eclipse developers.</p>
362 <p>The most common problems surrounding GCJ are:</p>
364 <li>Eclipse does not start at all</li>
365 <li>Eclipse throws a 'java.lang.ClassNotFoundException: org.eclipse.core.runtime.Plugin' that can be found in the logs (located in
366 workspace/.metadata/.log)</li>
369 <p>The workspace's log file is a good place to check to identify whether GCJ is
370 being used or not. Every Eclipse log session is prepended with
371 information about the runtime environment that was used to run Eclipse. The log
372 may include something like the following:</p>
374 <code>java.fullversion=GNU libgcj 4.2.1 (Debian 4.2.1-5)</code>
376 <p>If Eclipse does start, one can check which runtime environment is being used to
377 run Eclipse by going to <b>Help > About Eclipse SDK > Installation Details > Configuration</b>. The
378 <b>About</b> dialog itself can also provide other information, the build identifier
379 can be of particular interest as it is tagged by some distributions. This allows the
380 user to identify whether Eclipse was downloaded through the distribution's
381 package management system or directly from the eclipse.org web site.</p>
383 Eg: <code>Build id: M20070212-1330 (Ubuntu version: 3.2.2-0ubuntu3)</code>
385 <p>The two most common workarounds are:</p><ul>
386 <li>download the Eclipse binary from eclipse.org directly</li>
387 <li>run Eclipse using an alternate Java runtime environment</li></ul>
389 <p>To download Eclipse, try one of the links below:</p><ul>
390 <li><a href="http://www.eclipse.org/downloads/">http://www.eclipse.org/downloads/</a></li>
391 <li><a href="http://download.eclipse.org/eclipse/downloads/">http://download.eclipse.org/eclipse/downloads/</a></li></ul>
393 It is imperative that 64-bit builds are downloaded and used if a 64-bit Java
394 runtime environment has been installed. Below are two sample tarball names of
395 version 4.2 of the Eclipse SDK packaged for 32-bit and 64-bit processors.
397 <pre>eclipse-SDK-4.2-linux-gtk.tar.gz (32-bit)
398 eclipse-SDK-4.2-linux-gtk-x86_64.tar.gz (64-bit)</pre>
400 <p>To run Eclipse with an alternate Java runtime environment, the path to the Java
401 virtual machine's binary must be identified. With an Eclipse installation from
402 the distribution, altering the $PATH variable to include the path to the
403 alternate Java runtime environment is often not enough as the Eclipse that
404 Linux distributions package often performs a scan internally to pick up GCJ by
405 itself whilst ignoring what's on the $PATH. An example of the terminal's output
408 <code>searching for compatible vm...<br/>
409 testing /usr/lib/jvm/java-7-icedtea...not found<br/>
410 testing /usr/lib/jvm/java-gcj...found</code>
412 <p>Once the path to the virtual machine's binary has been identified, try running
413 Eclipse with the following command:</p>
415 <code>./eclipse -vm /path/to/jre/bin/java</code>
417 <p>For an actual example, it might look something like the following:</p>
419 <code>./eclipse -vm /usr/lib/jvm/sun-java-6/bin/java<br/>
420 ./eclipse -vm /opt/sun-jdk-1.6.0.02/bin/java</code>
422 <p>If this seems to solve the problem, it is likely that the problem really was
423 related to the use of GCJ as the Java runtime for running Eclipse. The
424 eclipse.ini file located within Eclipse's folder can be altered to
425 automatically pass this argument to Eclipse at startup. An example of its
426 content is presented below:</p>
428 <code>-showsplash<br/>
429 org.eclipse.platform<br/>
430 --launcher.XXMaxPermSize<br/>
433 /opt/sun-jdk-1.6.0.02/bin/java<br/>
438 <p>Note that every argument must be on its own line. More information about the
439 eclipse.ini file can be found at <a href="http://wiki.eclipse.org/Eclipse.ini">http://wiki.eclipse.org/Eclipse.ini</a>.</p>
441 <p>If problems persists after downloading an installation of Eclipse from
442 eclipse.org and using a supported Java runtime environment (a list of which may be found <a href="#TargetOperatingEnvironments">above</a>),
443 you can seek further assistance through the <a href="http://www.eclipse.org/newsgroups/">newsgroups</a>,
444 the IRC <a href="irc://irc.freenode.net/#eclipse">channel</a>,
445 and/or <a href="https://bugs.eclipse.org/bugs/">bugzilla</a>.
448 <h3>3.1.3 <a name="I-General-64bitJava">General - 64-bit Java HotSpot(TM) VM</a></h3>
450 There is a known issue with the Java HotSpot(TM) 1.6.0 VM compiler which causes eclipse to
451 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>,
452 and Eclipse bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=214092">214092</a>).
453 The crash usually occurs within a VM CompilerThread when attempting to compile the method org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith.
456 This problem has been addressed in Sun Java 6 update 11, so the simplest resolution is
457 to obtain the latest JRE release for your platform.
458 To work around the issue you can exclude the method org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith from being compiled with the following
463 -XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
467 This VM argument can be placed in the eclipse.ini file after the -vmargs line like the following:
472 plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090306-1900<br/>
473 --launcher.library<br/>
474 plugins/org.eclipse.equinox.launcher_1.0.200.v20090429-1630.jar<br/>
476 org.eclipse.platform<br/>
477 --launcher.XXMaxPermSize<br/>
480 -XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith<br/>
486 There have been reports of other classes that cause the compiler to crash. If all else fails you can
487 disable the compiler with the VM arg "-Xint".
490 <h3>3.2 <a name="I-Platform">Platform</a></h3>
492 <h3>3.2.1 <a name="I-Platform-Core">Platform - Core</a></h3>
494 <h4>Installing plug-ins by unzipping them into the plugins directory</h4>
495 <p>New plug-ins can be installed into the system by unzipping them into the plugins
496 directory. However this is not recommended, and the dropins directory should be
497 used for this purpose instead. Note that unzipping a different
498 version of a plug-in that is already installed will have no effect. To change the version
499 of a plug-in installed in your system, you need to either perform an update, or install
502 <h4>No branding with old config.ini</h4>
503 <p>If you have an old config.ini file and use it with a new Eclipse build, you
504 may not get the correct product branding. This is because the id of the standard
505 Eclipse product changed. Users in shared install scenarios may end up in this
506 situation as previous builds of Eclipse automatically generated config.ini files
507 in some cases. The work around is either to delete the local config.ini or
508 update the eclipse.product line to read eclipse.product=org.eclipse.platform.ide.</p>
510 <h4>Problems with classloaders in created threads</h4>
511 <p>There is a known issue with trying to load classes from a newly-created
512 thread using a class loader different from the plug-in class loader. The result
513 will be a <code>ClassNotFoundException</code>. As a workaround, do the
516 <li>Create a thread in which to run your code.</li>
517 <li>Send yourThread.setContextClassLoader(yourClassLoader); // you can find
518 your classloader by grabbing a class it loaded (YourPluginClass.class.getClassLoader())</li>
519 <li>Run your code in the newly created thread.</li>
521 <p>If you set the context class loader for the current thread, you are
522 competing with other users of the thread (all of Eclipse), so the results will
523 be unpredictable. However, there should be no problem in practice provided you
524 reset the context class loader back to its original value when your use in the
525 current thread is complete. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=8907">8907</a>)</p>
527 <h4>Deadlock creating executable extension in Plugin.startup</h4>
528 <p>If <code>Plugin.startup</code> code is too complex and performs tasks such
529 as creating an executable extension, a deadlock situation can be created. Only
530 simple bookkeeping tasks should be performed in <code>Plugin.startup</code>
531 code. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=5875">5875</a>)</p>
532 <h4>Potential Problems Converting Plug-in Manifests</h4>
533 <p>If your plug-in ships with a plug-in manifest and not an OSGi bundle manifest,
534 is shipped as a JAR file, and contains a nested JAR file then there may be
535 problems in the automatic generation of the bundle manifest file. The packages
536 defined in the nested JAR may not be exported correctly in the <tt>Export-packages</tt>
538 bundle manifest header. To work around this you should ship your plug-in with a
539 bundle manifest. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=97689">97689</a>)</p>
540 <h4>Location for Debug Options File on Mac OS</h4>
541 <p>If you are running in debug mode on Mac OS, the default location for the
542 .options file is inside the application bundle in the Eclipse.app/Contents/MacOS
543 directory (like the eclipse.ini). (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88782">88782</a>)</p>
545 <h4>Issues with JNI that use FindClass</h4>
547 There may be issues when using a JNI implementation that uses FindClass
548 in a function where the JNIEnv pointer is not available, such as in a C
549 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
550 class loader to find the class.
551 If the desired class is in the classpath used for the application classloader
552 (e.g. defined by the VM argument -cp <classpath>), as it would typically be in
553 a stand-alone application, there is no problem. However, under
554 Eclipse, the application classloader does not have access to classes
555 contained in plug-ins. Eclipse uses its own class loader to find classes
556 contained in plug-ins.
559 The proper plug-in class loader is used by FindClass in JNI functions which are
560 passed the JNIEnv pointer, but not when you have to use AttachCurrentThread to get the
561 JNIEnv pointer. In this case the application classloader is used.
564 For example, the following will fail because AttachCurrentThread is used to
565 get the JNIEnv pointer:</p>
567 static JavaVM* jvm; // Global variable
569 void myCallback(void) {
571 jvm->AttachCurrentThread((void**)&env, NULL);
572 // Fails if some/class is not in the application classloader:
573 jclass cls = env->FindClass("some/class");
574 jmethodID methodID = env->GetMethodID(cls, "methodName",
575 "(Ljava/lang/String;)V or whatever signature");
576 env->CallVoidMethod(callback, methodID, ...);
577 jvm->DetachCurrentThread();
582 A solution is to cache the method ID, for example:
585 static jmethodID mid; // Global variable
587 JNIEXPORT jint JNICALL JNI_OnLoad(JavaVM *vm, void *reserved) {
589 // Store the JavaVM pointer
592 // Find the class and store the method ID
593 // Will use the class loader that loaded the JNI library
594 jclass cls = env->FindClass(className"some/class");
597 mid = env->GetMethodID(cls, "methodName",
598 "(Ljava/lang/String;)V or whatever signature");
603 void myCallback(void) {
605 jvm->AttachCurrentThread((void**)&env, NULL);
606 env->CallVoidMethod(callback, mid, ...);
608 jvm->DetachCurrentThread();
613 <h3>3.2.2 <a name="I-Platform-Ant">Platform - Ant</a></h3>
614 <h4> Custom Ant tasks and Ant types must be separate from plug-in library JARs</h4>
615 <p>Including the class files for custom Ant tasks or Ant types in the regular
616 code JAR for your plug-in causes problems. These class files must be provided in
617 a separate JAR that is contributed to the <code>org.eclipse.ant.core.antTasks</code>
618 or <code>antTypes</code> extension point (and not declared as a library in the
619 plug-in's manifest). This ensures that the Ant tasks and types are loaded by the
620 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 <h4> Concurrent Ant builds not supported</h4>
623 <p>Eclipse can run Ant in the same JVM as the rest of Eclipse. Several aspects
624 of Ant and its use of global Java resources (such as System.out and System.err),
625 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>XDoclet support from within Eclipse</h4>
628 <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
629 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37070">37070</a>)</p>
631 <h4>Ant Editor code completion based on Ant 1.6.x</h4>
632 <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.
633 Code completion proposals are mostly based on Ant 1.6.x with some updates to Ant 1.8.3 (bug
634 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=193046">bug 193046</a>)</p>
636 <h4> Setting build loggers not supported when debugging Ant builds</h4>
637 <p>When debugging Ant builds within Eclipse, setting <code>-logger</code> as a program argument will be ignored.</p>
639 <h4>Renaming an External Tool builder set to run during auto-build will cause errors</h4>
640 <p>If you rename an existing external tool builder that is configured to run during auto-builds, you will get the following error:
642 Errors running builder "Integrated External Tool Builder" on project
643 <PROJECT_NAME>.
644 The builder launch configuration could not be found.
645 The workaround is to first disable the builder for auto-builds and then rename the builder.
646 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=118294">118294</a>)</p>
648 <h4>Slow typing/saving of the Ant editor with imports that define numerous macrodefs</h4>
649 <p>The Ant editor is slow on saving with buildfiles that have <import> declarations of buildfiles that have numerous <macrodef>s.
650 See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=125117">125117</a> for a possible workaround</p>
652 <h4>Failure to run Ant builds on non-Windows platforms if Eclipse installed in location with spaces in the path</h4>
653 <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.
654 Embedded usage of Ant builds, such as plug-in export will also fail.
655 See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=187993">187993</a> for possible workarounds</p>
657 <h4>Ant 1.8.x reports missing libraries as build failures</h4>
659 In Ant 1.8.x, if you try to use a task that requires additional libraries and you do not have the libraries on the Ant classpath, the build will now properly report as failed.
660 In previous versions of Ant, the build would still report that it had suceeded even though it actually failed to run any of the tasks from additional bundles. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=344518">bug 344518</a>.
663 For more information on tasks that require additional bundles please refer to the <a href="http://www.apache.org/dist/ant/RELEASE-NOTES-apache-ant-1.8.2.html">Ant 1.8.2 release notes</a>
664 and the <a href="http://ant.apache.org/manual/install.html#optionalTasks">Optional Tasks</a> section in the At manual.
667 <h3>3.2.3 <a name="I-Platform-User-Assistance">Platform - User Assistance</a></h3>
668 <h4>Welcome page not displayed properly (Linux/Unix)</h4>
669 <p>The default Welcome implementation is HTML-based and requires a supported browser
670 in order to work. If no supported browser can be found, Welcome falls back to its
671 Forms-based implementation, which has a different (simpler) appearance. Consult the
672 <a href="http://www.eclipse.org/swt/faq.php#browserplatforms">SWT FAQ</a> for supported
673 browsers and setting up your browser to work with eclipse.
676 <h4>Help browser tool bar buttons do not work for some documents</h4>
677 <p>The Help browser's Print, Synchronize, and Bookmark buttons do not work for
678 pages that are not actually installed with the product. However, you can always
679 use the print command in the browser's context menu to print the page you're
680 reading. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=44216">44216</a>)</p>
681 <h4> Help documents not displayed
682 in a browser or very slow document loading (Windows only)</h4>
684 If your LAN settings are not properly configured for local host access, your
685 Help browser might open to a blank page or display an HTTP error instead of a
686 help page, or you may experience long delays when loading help documents. Your
687 system administrator can configure your LAN settings so that help documents can
688 be accessed from the local help server.
691 <li>In the Control Panel, open <b>Internet Options</b>, select the <b>Connections</b>
692 tab and choose <b>LAN Settings</b>.</li>
693 <li>If your host was configured to use DHCP for IP assignment, make sure
694 that the "Automatically detect settings" check box is cleared.</li>
695 <li>If you use a proxy server, ensure that the "Bypass proxy server
696 for local addresses" is selected.</li>
697 <li>In "Advanced" settings for proxies, add
698 "127.0.0.1;localhost" to the "Exceptions" if these
699 addresses are not listed.</li>
700 <li>If you are using an automatic configuration script for proxy
701 settings, and are not sure that the script is correct, clear the "Use
702 automatic configuration script" check box.</li>
706 <h4> Working disconnected from
707 the network (Windows only)</h4>
708 If you are experiencing problems when not connected to the network, you must
709 install the loopback adapter from the Windows installation CD. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=831">831</a>)
710 <h4> Using Internet Explorer in
711 offline mode (Windows only)</h4>
713 If you have been using Internet Explorer in Offline mode, when you access the
714 help system you will get a message indicating that the web page you requested is
715 not available offline or a blank page will display. Click <b>Connect</b> or
716 deselect "Work Offline" in the Internet Explorer "File" menu
717 to return the system behavior to normal.
718 <h4>Help topics not highlighted in High Contrast mode (Windows only)</h4>
719 <p>Windows High Contrast settings are not consistently picked up by Internet
720 Explorer when they are set from the Accessibility Options utility as opposed to
721 when they are set using the predefined schemes. On Windows XP, it is recommended
722 to set High Contrast as follows: Right click the desktop, chose properties,
723 select Windows Classic style from the Windows and buttons drop down on the
724 Appearance tab, and choose your scheme (for example High Contrast Black) from
725 Color Scheme drop down. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=28609">28609</a>)</p>
727 <h3>3.2.4 <a name="I-Platform-UI">Platform - UI</a></h3>
728 <h4>High contrast settings</h4>
729 <p>Eclipse was tested for High Contrast using 1152 x 864 resolution in Windows
730 XP High Contrast mode. You can select this mode by selecting Accessibility
731 Options > Display > Use High Contrast from the Windows XP Control Panel
734 <h4> Dirty state not tracked properly for OLE documents (Windows only)</h4>
735 <p>The dirty state for an OLE document is not updated properly. This causes
736 Eclipse to prompt to save the contents of the editor when the document is
737 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>
738 <h4> OLE document crashes can cause Eclipse to also crash (Windows only)</h4>
739 <p>If an OLE document crashes, Eclipse can crash, or the workbench menus can
740 become inconsistent.</p>
741 <h4>Toolbars only containing contributed controls exhibit display errors on Mac/Linux</h4>
743 Currently there is no way on the Max or Linux platforms to define the <b>height</b> for controls contributed to
744 toolbars, nor will those platforms respect the size returned by the control's <code>computeSize</code> method. If you
745 encounter this issue there is currently no truly viable workaround.
746 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=183003">183003</a>)
748 <h4>Customizing menus and toolbars not working reliably</h4>
750 The Customize Perspective Dialog can still be used to turn on action sets in the Command Groups Availability tab,
751 but the items contained within the action sets are no longer displayed in the dialog. The Toolbar Visibility
752 and Menu Visibility no longer display the correct information or icons, and will not work correctly.
753 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=378845">378845</a>)
755 <h4>Cannot launch a workbench with "-data @none"</h4>
757 Eclipse 3.x RCP apps cannot be launched with no workspace. The workaround is to supply a /tmp directory to
758 <b>-data</b> when launching.
759 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=380853">380853</a>)
761 <h4>Launching an inner eclipse can lead to PermGen errors</h4>
763 On some Oracle JVMs, launching an inner eclipse during plug-in development can lead to PermGen errors
764 for the inner eclipse. The native launcher checks the JVM and can add <i>-XX:MaxPermSize=256m</i>,
765 but PDE launches simply use java and don't go through the native launchers. The workaround is to add
766 the appropriate JVM arg to your launch config or to the <i>Preferences > Java > Installed JREs</i>.
767 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=339763">339763</a>)
769 <h4>Eclipse doesn't exit dragging mode</h4>
771 Sometimes after releasing the mouse while dragging a part, eclipse doesn't exit drag mode.
772 The workaround is to hit <b>ESC</b>.
773 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=379590">379590</a>)
775 <h4>Some key shortcuts stop working after switching schemes</h4>
777 Sometimes after switching schemes (to and from Emacs) some keys will stop working or not function
778 correctly (CTRL+L, CTRL+K, CTRL+A, etc).
779 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=378684">378684</a>)
781 <h4>Capabilities and Activities don't affect the menus and toolbars</h4>
783 Capabilities used to hide GUI elements like menu entries won't work yet, as Capabilities have not
784 been fully implemented in the 4.2 Workbench.
785 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=359778">359778</a>)
788 <h3>3.2.5 <a name="I-Platform-Text">Platform - Text</a></h3>
791 <h3>3.2.6 <a name="I-Platform-SWT">Platform - SWT</a></h3>
792 <h4>Eclipse plug-in based on the SWT Browser throws exception</h4>
793 <p>The SWT Browser widget uses a platform-specific web browser to render HTML.
794 The org.eclipse.swt.SWTError exception ("No more handles") is thrown
795 on platforms that don't meet the requirements for running the Browser widget.
796 Supported platforms and prerequisites are listed on the SWT FAQ item <a href="http://www.eclipse.org/swt/faq.php#browserplatforms">
797 "Which platforms support the SWT Browser?"</a>.</p>
799 <h4>Opening File Dialog crashes eclipse (Vista only)</h4>
800 <p>On Vista, launching eclipse using <code>-vmargs -Xmx[any size]</code> can crash eclipse when the FileDialog is opened.
801 The workaround is to use the default heap size, i.e. do not use the <code>-Xmx</code> VM args.
802 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=188317">188317</a>)</p>
804 <h4>Crash while editing text (Windows XP with SP2 only)</h4>
805 <p>Some users who have installed Service Pack 2 on Windows XP have experienced
806 crashes while using editors in Eclipse. The workaround is to place a working version
807 of Windows\System32\USP10.DLL in the Eclipse startup directory or uninstall
809 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=56390">56390</a>)</p>
811 <h4>Eclipse hangs when pasting from an unresponsive application (GTK only)</h4>
812 <p>If the application that is supplying the clipboard material is unresponsive,
813 the paste operation hangs Eclipse for several minutes. This situation can be
814 encountered when copying from an Eclipse target workbench, suspending the target
815 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>
817 <h4>IME conversion problem (Solaris GTK only)</h4>
818 <p>When typing Japanese text, the conversion to Kanji must be done one ideogram at
819 a time. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=226636">226636</a>)</p>
821 <h4>Typing in an editor crashes with IBM 1.5 VM (Linux GTK PPC only)</h4>
822 <p>When running on the IBM Java 5.0 VM, Eclipse crashes while the user is typing in an editor.
823 If using this VM you must disable the JIT with the -Xnojit vm argument to avoid the crashes
824 (see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=116730">116730</a>).
825 The command line for launching Eclipse with this vm should be: <br/>
826 <code>eclipse -vmargs -Dosgi.locking=none -Xnojit</code>
829 <h4>Eclipse won't start (Linux GTK PPC only)</h4>
830 <p>Eclipse fails to create a lock file with reason "No locks available".
831 To launch eclipse you must disable file locking using the osgi.locking property.
832 For example, you could launch eclipse as follows: <br/>
833 <code>eclipse -vmargs -Dosgi.locking=none</code>
836 <h4>Strings may be truncated or incorrectly wrapped on RHEL5 (Linux GTK only)</h4>
838 Strings on wrapping Controls may not appear correctly in some locales on RHEL5 as a result
839 of a bug in Pango version 1.14.x. This problem can be fixed by upgrading the installed
840 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>)
843 <h4>Block Selection functionality provided by StyledText is not BIDI aware</h4>
845 When the orientation of characters under the left and right edges of the block
846 selection rectangle are not the same, the actual selection ranges (in memory)
847 differ from the visual representation of the selection. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=277929">277929</a>)
850 <h4>Older versions of some Windows screen readers no longer work with Eclipse</h4>
851 <p>JAWS versions 8 and 9 and Window-Eyes version 6 no longer work well with Eclipse and other SWT applications.
852 Window-Eyes 6 will cause Eclipse to crash, and JAWS 8 and 9 can cause SWT applications to crash.
853 This happens because IAccessible2 support was added to SWT for Eclipse 3.7, but these older screen reader versions contain
854 partial implementations of IAccessible2 that do not follow the current IAccessible2 specification.</p>
856 The workaround for these cases is to specify Java property <code>org.eclipse.swt.accessibility.UseIA2</code> with value <code>false</code>,
857 which will instruct SWT to not attempt to use IA2 interfaces. An easy way to set this property is to specify VM argument
858 <code>-Dorg.eclipse.swt.accessibility.UseIA2=false</code> when launching Eclipse or your SWT application. (bug
859 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=313182">313182</a>)</p>
861 <h4>Drawing problems when using non-advanced graphics on recent GTK versions</h4>
862 <p>On modern Linux distributions with a GTK version greater than 2.18, clipping problems and pixel corruption
863 can occur if the SWT client uses non-advanced GC calls. These problems seem to be caused by low-level bugs
864 in the interactions between GDK and X.
867 <h4>Menus do not appear in Unity desktop menu bar</h4>
868 <p>On recent Ubuntu Linux distributions that feature the Unity desktop, the menus from the workbench
869 will not appear in the top desktop menu bar. They will continue to appear in the shell.</p>
871 <h4>Slider controls do not draw on Ubuntu</h4>
872 <p>Sliders do not work on Linux distros with overlay scrollbars enabled (such as
873 Ubuntu 12.04). A workaround for this is to disable the overlay scrollbars
874 (export LIBOVERLAY_SCROLLBAR=0 ) before launching Eclipse.</p>
876 <h4>BIDI Segments in Text controls</h4>
877 <p>BIDI Segments in text controls only work on Windows and GTK.</p>
879 <h4>Toolbar controls on GTK are not properly sized</h4>
881 <p>There is a known problem in ToolItem that prevents control set in separators
882 from being sized properly. (See Bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=377961">377961</a>)
885 <h4>Navigation using tab and arrow keys</h4>
887 Navigating directly to a specific view or editor using keyboard shortcuts is the
888 same in Eclipse 4.x as it was in Eclipse 3.x with the exception of tab traversal.
889 In Eclipse 3.x, tab, shift+tab, ctrl+tab and ctrl+shift+tab always traversed within
890 a view or editor stack. In 4.x, these keys traverse through all of the view and editor stacks.
891 When traversing in the forward direction (tab or ctrl+tab), the active view or editor
892 will take focus. When navigating in the reverse direction, other elements of a view,
893 such as the view toolbar or menu, can take focus as well. This behavior can be a
894 little quirky, and we are looking into normalizing it for 4.2.1
895 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=376011">376011</a>)
898 <h3>3.2.7 <a name="I-Platform-Team-CVS">Platform - Team - CVS</a></h3>
899 <p>The following are known problems with the CVS repository provider only, and
900 do not apply to other repository providers. Additional information on how to use
901 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
903 <h4> CVS server compatibility</h4>
904 <p>The CVS plug-in parses messages returned from the CVS server. If the format
905 of these messages is not as expected, some of the plug-in's functionality may be
906 missing. The CVS plug-in is compatible with all stable 1.11.X builds of the CVS
907 server, and should be compatible with future releases in that stream unless text
908 message formats change (the last tested server was 1.11.22). As for the 1.12.X
909 feature releases of CVS, the Eclipse CVS client has been tested with builds up
910 to 1.12.13. However, future releases could easily break the Eclipse CVS client.
911 Basic functionality, such as Checkout, Commit, and Update, should always work,
912 but there may be problems with more advanced commands such as Synchronizing and
913 Browsing the repository.</p>
915 <h4>SSH2 proxy settings lost upgrading to 3.3</h4>
916 <p>CVS now uses the Platform proxy settings. As a result, any CVS proxy settings
917 will be lost and must be re-entered on the General>Network Connections preference
919 <h4>Connection cannot be found after initially missing</h4>
920 <p>If a connection initially fails due to a network problem, the connection may
921 continue to fail even when the network problem is fixed. In order to establish
922 the connection you must exit and restart Eclipse. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=9295">9295</a>)</p>
924 <h4>"Received broken pipe signal" error from server</h4>
925 <p>Eclipse sometimes performs multiple commands within a single connection to
926 the server. This may cause problems with CVS servers that are running server
927 scripts in response to certain commands. (bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=23575">23575</a>
928 and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=23581">23581</a>)</p>
930 <h4>"Terminated with fatal signal 10" error from server</h4>
931 <p>There is a bug in the CVS server related to some compression levels. If you
932 get this error, changing the compression level on the CVS preference page may
933 help. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=15724">15724</a>)</p>
934 <h4>"Unknown response" error using ext connection method</h4>
935 <p>There are a few situations that can result in an "Unknown response"
936 error messages when using the ext connection method. One situation involves
937 using an external communications client (e.g. rsh or ssh) that adds CRs to the
938 communications channel (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=21180">21180</a>).
939 Another involves Eclipse not properly reading the stderr output of the external
940 communications tool. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=11633">11633</a>)</p>
942 <h4>A disabled CVS capability may not be auto-enabled in existing workspaces</h4>
943 <p>New in 3.0 is the ability to disable capabilities and the CVS support in
944 Eclipse can be disabled. However, for backwards compatibility the CVS capability
945 is auto-enabled in existing workspaces that already contain CVS projects. The
946 auto-enabling function may not run if the team support plugin is not loaded at
947 startup. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66977">66977</a>)</p>
948 <h4>Builder output files may appear as changed</h4>
949 <p>When folders containing build output are shared they may get improperly
950 marked as dirty when build output is generated.</p>
952 <h4>Enabling GNOME proxy support</h4>
953 <p>GNOME applications can make use of proxy settings defined in this environment.
954 If set, Eclipse will use it prior to proxy settings declared using env variables.
955 This feature is disabled by default, to enable it launch Eclipse with
956 <code>"-Dorg.eclipse.core.net.enableGnome"</code> switch. That is,</p>
957 <pre>eclipse -Dorg.eclipse.core.net.enableGnome</pre>
959 <h3>3.2.8 <a name="I-Platform-Install-Update">Platform - Install/Update</a></h3>
960 <h4>Manually installing features and plug-ins on a FAT file system (Windows only)</h4>
962 <p>When features and plug-ins are manually installed on top of an Eclipse-based
963 product install located on a FAT file system that has already been run at least
964 once, the product must be explicitly restarted with -clean. That is,</p>
965 <pre>eclipse.exe -clean
968 <h4>Connecting to untrusted sites using https</h4>
969 <p>You cannot install or update software from a site using https whose certificate
970 is not chained to a trusted root certificate in your local certificate store. This typically
971 means the server is using a self-signed certificate, or a certificate authenticated by
972 an unknown third party.</p>
974 <h4>Extension location is lost if the install path changes</h4>
975 <p>A previously configured extension location may be temporarily removed if the install is moved or mounted
976 under a different path. This only happens when the link file that configures the
977 extension location uses a relative path that points to a directory under the Eclipse
978 install. On a second startup using the same install path, the extension location
979 is added again (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95403">95403</a>). <br/></p>
981 <h4>Feature patches can only be installed from Eclipse 3.4-based update sites</h4>
982 <p>Feature patches can only be installed from update sites designed for Eclipse 3.4 or greater.
983 Specifically, the update site must have the necessary metadata for Equinox p2 (a content.xml
984 or content.jar file). This data can be generated by building an update site using Eclipse 3.4
985 or newer, or running the p2 metadata generator on an update site built using earlier versions
986 of the Eclipse SDK. See the help topic <i>Generating p2 metadata</i> for more details on running the p2 metadata
987 generator (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=244483">244483</a>).
990 <h3>3.2.9 <a name="I-Platform-Debug">Platform - Debug</a></h3>
991 <p>None. (Known problems with the Java debugger appear below in the <a href="#I-JDT">JDT</a>
994 <h3>3.2.10 <a name="I-Platform-Compare">Platform - Compare</a></h3>
997 <h3>3.3 <a name="I-JDT">Java development tools (JDT)</a></h3>
999 <h4>Multiple regions formatting in a given source snippet</h4>
1000 In version 3.4, the new API method <code>org.eclipse.jdt.core.formatter.CodeFormatter.format(int, String, IRegion[], int, String)</code>
1001 has been added to allow the formatting of several regions in a source snippet with a single pass.<br/>
1002 Even if specified, this method does not currently accept comments of the following kinds:
1004 <li><code>org.eclipse.jdt.core.formatter.CodeFormatter#K_SINGLE_LINE_COMMENT</code></li>
1005 <li><code>org.eclipse.jdt.core.formatter.CodeFormatter#K_MULTI_LINE_COMMENT</code></li>
1006 <li><code>org.eclipse.jdt.core.formatter.CodeFormatter#K_JAVA_DOC</code></li>
1008 This will be fixed in a future release (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=233967">233967</a>).
1010 <h4>Searching for constant field references</h4>
1011 <p>Search does not find references to constant fields inside binaries because
1012 the Java Language Specification mandates that constant field values be inlined
1013 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>
1015 <h4> Cut, copy, paste not working
1016 for linked resources in views showing Java elements</h4>
1017 <p>The cut, copy, and paste actions do not work for linked files and folders
1018 appearing in views that show Java elements, including the Package Explorer. The
1019 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>
1020 <h4> Java working sets not
1021 working correctly for elements from JRE system library container</h4>
1022 <p>Applying a working set consisting entirely of elements from the JRE System
1023 library container as a filter to the packages view might result in an empty
1024 Package Explorer. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=30442">30442</a>)</p>
1026 <h4>Breakpoints unreliable running Sun 1.6.0_14</h4>
1027 Developers debugging applications on Sun's 1.6.0_14
1028 virtual machine should be aware that breakpoints are unreliable (i.e. do
1029 not always suspend execution). The problem occurs on Windows and Linux
1030 platforms. This is an issue with the VM and not with Eclipse.
1031 The workaround is to use the <code>-XX:+UseParallelGC</code> VM option. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=279137">279137</a>).
1033 <h4>Some refactoring script operations fail with Sun 6.0 JREs</h4>
1034 <p>Creating and applying refactoring scripts sometimes fails with Sun 6.0 JREs
1035 due to a bug in the XML parser that is shipped with those VMs.
1036 A workaround is to use a J2SE 5.0 VM or an IBM 6.0 VM.
1037 Another workaround is to replace the XML parser using the
1038 <a href="http://download.oracle.com/javase/6/docs/technotes/guides/standards/index.html">Java Endorsed Standards Override Mechanism</a>:
1041 <li>Get original versions of xml-apis.jar, xercesImpl.jar, xalan.jar, and serializer.jar from Apache, e.g.
1042 xalan-j_2_7_1-bin.zip from <a href="http://xml.apache.org/xalan-j/downloads.html">here</a>.
1044 <li>Unpack the archive and copy the 4 JARs into <code><path-to-your-JavaSE6.0-install>\jre\lib\endorsed\</code>.
1047 (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>,
1048 Eclipse bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=262820">262820</a>)
1050 <h4>Suspend on uncaught exception overrides exception breakpoint location filters</h4>
1051 <p>Exception breakpoints can be configured with location filters (inclusive and
1052 exclusive). When an unchecked exception is configured to <b>not</b> suspend
1053 execution in a specific class, execution will still suspend when the user preference
1054 to suspend on uncaught exceptions is on. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66770">66770</a>)</p>
1056 <h4>Running Java programs with non-Latin-1 characters in package or class names</h4>
1057 You get a <code>java.lang.NoClassDefFoundError</code> when running Java
1058 programs with non-Latin characters in the package or class names. The workaround
1059 is to package the class files as a JAR file and run the program out of the JAR
1060 and not from the file system directly. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=4181">4181</a>)
1062 <h4>Cannot run or debug class in
1063 a project with GB18030 characters in project name</h4>
1064 <p>Most class libraries do not properly support the creation of a system
1065 process (via <code>java.lang.Runtime.exec(...)</code>) when the specified
1066 command line contains GB18030 characters. This limitation means the debugger
1067 cannot launch applications when the command line it generates contains GB18030
1068 characters. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32206">32206</a>)</p>
1070 <h4>Cannot detect installed JRE with GB18030 characters in path name</h4>
1071 <p>Automatic JRE detection fails when the JRE is stored in a directory
1072 containing GB18030 characters in its name. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=33844">33844</a>)</p>
1074 <h4>Cannot generate Javadoc for packages with GB18030 characters in the name</h4>
1075 <p>Most class libraries do not properly support the creation of a system
1076 process (via <code>java.lang.Runtime.exec(...)</code>) when the specified
1077 command line contains GB18030 characters. Since Javadoc is created using the
1078 Javadoc executable provided with the JDK, generating Javadoc fails if the
1079 package or class name contains GB18030 characters. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32215">32215</a>)</p>
1081 <h4> Unable to debug stack
1084 <p>If a debug session suspends on a <code>java.lang.StackOverflowError</code>
1085 exception (due to an exception breakpoint), the debugger may not be able to
1086 retrieve any debug information from the target JVM. As well, the debugger may
1087 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>
1088 <h4> Evaluation limitation</h4>
1089 <p>The debugger uses threads in the target JVM to perform evaluations (both
1090 explicit evaluations that the user requests, and implicit evaluations such as <code>toString()</code>
1091 invocations in the <b>Variables</b> view). The Java Debug Interface (JDI)
1092 requires that the thread in which an evaluation is performed be suspended by a
1093 user event (that is, a breakpoint or step request). Evaluations cannot be
1094 performed on threads suspended by the suspend action. As well, when a breakpoint
1095 is configured to suspend the JVM rather than just the individual thread, the
1096 threads which did not encounter the breakpoint are not in a valid state to
1097 perform an evaluation. When an evaluation is attempted in a thread that is not
1098 in a valid state to perform an evaluation, an error message will appear to the
1099 effect of "Thread must be suspended by step or breakpoint to perform method
1100 invocation". (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34440">34440</a>)</p>
1102 <h4> Missing debug attributes</h4>
1103 The debugger requires that class files be compiled with debug attributes if
1104 it is to be able to display line numbers and local variables. Quite often, class
1105 libraries (for example, "<code>rt.jar</code>") are compiled without
1106 complete debug attributes, and thus local variables and method arguments for
1107 those classes are not visible in the debugger.
1108 <h4> Using Hot Code Replace</h4>
1109 <p>Hot code replace is supported on JDK 1.4.x VMs, and IBM J9 VMs. The debugger
1110 will attempt to replace all class files that change in the workspace as the user
1111 edits and builds source code. However, hot code replace is limited to changes
1112 that a particular virtual machine implementation supports. For example, changes
1113 within existing methods may be supported, but the addition or removal of members
1116 Setting a breakpoint inside a scrapbook page is not supported.
1118 <p>When a snippet is run in the scrapbook which directly or indirectly calls <code>System.exit(int)</code>,
1119 the evaluation cannot be completed, and will result in a stack trace for a <code>com.sun.jdi.VMDisconnectedException</code>
1120 being displayed in the scrapbook editor.</p>
1121 <p>Terminating a scrapbook page while it is performing an evaluation results
1122 in a <code>com.sun.jdi.VMDisconnectedException</code> being displayed in the
1123 scrapbook editor.</p>
1124 <h4> Debugging over slow
1126 A global Java debug preference specifies the debugger timeout, which is the
1127 maximum amount of time the debugger waits for a response from the target VM
1128 after making a request of that VM. Slow connections may require that this value
1129 be increased. The timeout value can be edited from the <b>Java > Debug </b>preference
1130 page. Changing the timeout value only affects subsequently launched VM, not VMs
1131 that are already running.
1133 <h4> Updating of inspected values</h4>
1134 When inspecting the result of an evaluated expression in the debugger, it is
1135 important to note that the result displayed is the result of that expression at
1136 the time it was evaluated. For example, when inspecting a simple integer counter
1137 (primitive data type), the value displayed in the Expressions view is the value
1138 when the expression was evaluated. As the counter is changed in the running
1139 program, the inspected result will not change (since the view is not displaying
1140 the value bound to a variable - it is displaying the value of an expression, and
1141 the value of a primitive data type cannot change). However, if an expression
1142 results in an object, fields of that object will be updated in the inspector as
1143 they change in the running program (since the value bound to fields in an object
1145 <h4> Stepping over native methods
1146 that perform I/O</h4>
1147 When the debugger steps over native methods that perform I/O to <code>System.out</code>
1148 or <code>System.err</code>, the output may not appear immediately unless the
1149 native performs a flush on the output buffer.
1150 <h4> VM and process termination
1151 running on IBM 1.3 JVM on Linux (Linux only)</h4>
1152 Terminating a launch, debug target, or system process associated with a debug
1153 target running on the IBM 1.3 JVM on the Linux platform does not work when the
1154 associated debug target has a suspended thread. To remove such debug targets
1155 from the debug UI, select <b>Terminate and Remove</b> from the debug view's
1156 pop-up menu (or use the shortcut "delete" key). Associated system
1157 processes in the OS may not be properly cleaned up. If a debug target has no
1158 suspended threads, termination works properly. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=1631">1631</a>)
1160 <h4>Java 6 and MacOS</h4>
1161 Apple JavaSE-1.6 VMs only execute on 64-bit architectures but JDT will detect 1.6 VMs installed on 32-bit
1162 architectures when a new workspace is started or when the user presses the "Search..." button
1163 on the Installed JREs preference page. Error messages will appear in the log each time JDT attempts to
1164 determine which execution environments a 1.6 VM is compatible with. JDT can be configured to ignore 1.6
1165 JREs by removing them from the Installed JREs preference page.
1166 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=262542">262542</a>)
1168 <h4>Java Annotation Processing</h4>
1169 <p>Some methods in the processing API are unimplemented when compiling within the IDE, and will
1170 throw <code>UnsupportedOperationException</code>.</p>
1172 Java 6 annotation processors are supported in the batch compiler and in the
1173 IDE. By design, Java 6 processors are only executed during a build, not while
1174 editing. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=188558">188558</a>)</p>
1176 Java 5 annotation processors are supported in the IDE only. Java 5 processors
1177 can be executed while editing, as well as during a build. Slow annotation
1178 processors can cause a slowdown of the editing experience. If this occurs, you
1179 may wish to turn off <b>Enable processing in editor</b> on the <b>Java Compiler > Annotation Processing</b> properties
1180 page of your Java project.</p>
1182 <h4>Java indexing encounters problems when a folder is used both as a source and a class folder</h4>
1183 <p>Java indexing encounters problems when a folder is used both as a source folder
1184 in a project and as a class folder in another project. Hence, when this peculiar setup is
1185 used, the Java Search might miss matches located in such a folder. To avoid this kind of problem, it is strongly advised to use different
1186 folders for sources and binary classes. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=309903">309903</a>)</p>
1188 <h3>3.4 <a name="I-PDE">Plug-in Development Environment (PDE)</a></h3>
1189 <h4>Feature manifest editor does not preserve all comments</h4>
1191 <p>When a non-source page of the feature manifest editor is used, PDE will convert
1192 changes back into XML by regenerating the file. Although the overall content and
1193 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>
1194 <h4>PDE will not unzip source zips of some plug-ins</h4>
1195 <p>In the plug-in import wizard, when you choose to import plug-ins as
1196 "projects with source folders", PDE will not unzip the source for the
1197 org.apache.ant, org.eclipse.core.runtime.compatibility.registry, org.eclipse.osgi.util and org.eclipse.osgi.services. This is
1198 because the source ZIPs contains code that will not compile when unzipped as it
1199 requires additional JARs that are not part of the SDK. To avoid the creation of
1200 plug-in projects that won't compile, PDE will import these plug-ins as binary
1201 and attach source, so you would still be able to read the source, you just won't
1202 be able to modify it. Also, PDE will not unzip the source for the
1203 org.eclipse.swt plug-ins. In this case, it is because, when shipped, the swt
1204 code is spread across a plug-in and a fragment, and when unzipped, it will
1205 require circular dependencies between the plug-in and fragment projects. These
1206 circular dependencies are at minimum marked as warnings by the JDT compiler and
1207 may result in unpredictable build behavior. Therefore, PDE always imports
1208 org.eclipse.swt as binary with source attached. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66314">66314</a>)</p>
1210 <h4>Emacs key bindings do not
1211 work in manifest editor fields</h4>
1212 <p>Non-default key bindings currently do not work in fields on non-source
1213 pages of the PDE manifest editors. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=19482">19482</a>)</p>
1215 <h4>Export of plug-in may silently drop classes</h4>
1216 <p>When exporting a plug-in using the plug-in, feature or product wizards, some classes
1217 might be dropped from the resulting archive if their fully qualified name is too long.
1218 This typical path limitation can be worked around by creating the jar of the problematic
1219 plug-in by using the Jar export wizard.
1220 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=97150">97150</a>)</p>
1222 <h4>Compilation errors when exporting projects not stored outside of the workspace</h4>
1223 <p>When exporting multiple plug-ins and one is stored outside of the workspace,
1224 compile errors occurs on export. To work around the problem, you can either export
1225 the plug-ins one by one, or change their location.
1226 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=98579">98579</a>)</p>
1228 <h4>Headless build needs to be run from a fully qualified path</h4>
1229 <p>When running a headless build using the scripts provided by pde build, the properties <code>builder</code>
1230 and <code>buildDirectory</code> must refer to a fully qualified path.
1231 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139554">139554</a>)
1234 <h4>Importing in Eclipse application fails if plug-in exists in host workspace</h4>
1235 <p>When running an Eclipse application (self-hosting) importing plug-ins will not
1236 work correctly if the plug-in being imported exists in the host Eclipse's
1237 workspace. This is because PDE modifies the target platform of the application
1238 to point at the running plug-ins from the host (target weaving). This also
1239 affects the PDE test suite.
1240 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=294005">294005</a>)
1243 <h4>Reusing a workspace after changing architectures silently breaks PDE models</h4>
1244 <p>If a workspace is reused on a machine with a different architecture, the PDE
1245 models used to build plug-ins may silently fail. To work around this problem,
1246 delete the metadata in <workspace>/.metadata/.plugins/org.eclipse.pde.core.
1247 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=350172">350172</a>)
1250 <h2>4. <a name="RunningEclipse">Running Eclipse</a></h2>
1251 <p>After installing the Eclipse SDK in a directory, you can start the Workbench
1252 by running the Eclipse executable included with the release (you also need a Java SE 6
1253 JRE, not included with the Eclipse SDK). On Windows, the executable file is called <samp>eclipse.exe</samp>,
1254 and is located in the <code>eclipse</code> sub-directory of the install. If
1255 installed at <code>c:\eclipse-SDK-4.2-win32</code>, the executable is <code>c:\eclipse-SDK-4.2-win32\eclipse\eclipse.exe</code>.
1257 <b>Note:</b> Set-up on most other operating environments is analogous. Special
1258 instructions for Mac OS X are listed <a href="#macosx">below</a>.</p>
1260 <h3>Allocating enough memory and solving OutOfMemoryErrors</h3>
1261 <p>By default, Eclipse will allocate up to 512 megabytes of Java heap memory. This should
1262 be ample for all typical development tasks. However, depending on the JRE
1263 that you are running, the number of additional plug-ins you are using, and
1264 the number of files you will be working with, you could conceivably have to increase this amount.
1265 Eclipse allows you to pass arguments directly to the Java VM using the
1266 <code>-vmargs</code> command line argument, which must follow all other Eclipse specific arguments.
1267 Thus, to increase the available heap memory, you would typically use:</p>
1269 <p><code>eclipse -vmargs -Xmx<memory size></code></p>
1271 <p>with the <code><memory size></code> value set to greater than
1272 "512M" (512 megabytes -- the default).
1275 When using an Oracle VM, you may also need to increase the size of the permanent
1276 generation memory. The default maximum is 64 megabytes, but more may
1277 be needed depending on your plug-in configuration and use. When the VM runs
1278 out of permanent generation memory, it may crash or hang during class loading.
1279 This failure is less common when using Oracle JRE version 1.5.0_07 or greater.
1280 The maximum permanent generation size is increased using the -XX:MaxPermSize=<memory size> argument:</p>
1282 <p><code>eclipse -vmargs -XX:MaxPermSize=<memory size></code></p>
1284 <p>This argument may not be available for all VM versions and platforms; consult your VM documentation
1288 Note that setting memory sizes to be larger than the amount of available physical
1289 memory on your machine will cause Java to "thrash" as it copies objects
1290 back and forth to virtual memory, which will severely degrade your performance.
1292 <h3>Selecting a workspace</h3>
1293 <p>When the Workbench is launched, the first thing you see is a
1294 dialog that allows you to select where the workspace will be located. The
1295 workspace is the directory where your work will be stored.
1296 If you do not specify otherwise, Eclipse creates the workspace in your
1298 This workspace directory is used as the default content area for your projects
1299 as well as for holding any required metadata. For shared or multi-workspace
1300 installs you must explicitly specify the location for your workspace using the
1301 dialog (or via the "<code>-data</code>" command line argument).</p>
1302 <h3>Specifying the Java virtual machine</h3>
1303 <p>Here is a typical Eclipse command line: </p>
1306 <p><code>eclipse -vm c:\jdk6u22\jre\bin\javaw</code></p>
1308 <p><i>Tip:</i> It's generally a good idea to explicitly specify which Java VM to
1309 use when running Eclipse. This is achieved with the "<code>-vm</code>"
1310 command line argument as illustrated above. If you don't use "<code>-vm</code>",
1311 Eclipse will look on the O/S path. When you install other Java-based products,
1312 they may change your path and could result in a different Java VM being used
1313 when you next launch Eclipse.</p>
1314 <p>To create a Windows shortcut to an installed Eclipse:</p>
1316 <li>Navigate to <code>eclipse.exe</code> in Windows Explorer and use Create
1317 Shortcut on the content menu.</li>
1318 <li>Select the shortcut and edit its Properties. In the Target: field append
1319 the command line arguments.</li>
1321 <p>Opening this shortcut launches Eclipse. (You can drag the shortcut to the
1322 Windows Desktop if you want to keep it in easy reach.)</p>
1324 <h3><a name="macosx">Mac OS X</a></h3>
1325 <p>On Mac OS X, you start Eclipse by double clicking the Eclipse application. If you need to
1326 pass arguments to Eclipse, you'll have to edit the <code>eclipse.ini</code> file
1327 inside the Eclipse application bundle: select the Eclipse application bundle icon while holding down the Control Key.
1328 This will present you with a popup menu. Select "Show Package Contents" in the popup menu.
1329 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.
1333 On MacOS X you can only launch a UI program more than once if you have separate
1334 copies of the program on disk. The reason for this behavior is that every UI
1335 application on Mac can open multiple documents, so typically there is no need
1336 to open a program twice. Since Eclipse cannot open more than one workspace, this means you have to make
1337 a copy of the Eclipse install if you want to open more then one workspace at
1338 the same time (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139319">139319</a>).
1341 <p>If you need to launch Eclipse from the command line, you can use the symbolic link "eclipse" in the
1342 top-level eclipse folder. It refers to the eclipse executable inside the application bundle and takes
1343 the same arguments as "eclipse.exe" on other platforms.
1345 <p>On Mac OS X 10.4 and later, you may notice a slow down when working with significant
1346 numbers of resources if you allow Spotlight to index your workspace. To prevent this, start
1347 System Preferences, select the Spotlight icon, then the Privacy tab, then click the Add button
1348 ("+") and find your workspace directory in the dialog that appears.</p>
1349 <h3><a name="SharedInstall">Shared Install</a></h3>
1350 <p>The startup speed of a shared install can be improved if proper cache information is stored in the shared
1351 install area. To achieve this, after unzipping Eclipse distribution, run Eclipse once with the "-initialize"
1352 option from an account that has a write access to the install directory.</p>
1353 <h2>5. <a name="Upgrading"></a>Upgrading Workspace from a Previous Release</h2>
1355 <h3>Users who don't use "-data"</h3>
1356 <p>If you weren't previously using "-data" to specify your workspace,
1357 follow these steps to upgrade:</p>
1360 <li>Find the workspace directory used by your old version of Eclipse.
1361 Typically this is located inside the directory in which Eclipse was
1362 installed in a sub-directory called "<code>workspace</code>". If
1363 you are using a shortcut or script to launch Eclipse, then it will be under
1364 the current working directory of that shortcut or script in a sub-directory
1365 called "workspace". For Windows users, this is specified by the
1366 "Start in:" argument in your shortcut properties.</li>
1367 <li>Copy this workspace directory to a new, empty location outside of any
1368 Eclipse install directory.</li>
1369 <li>Install the new version of Eclipse in a new location, separate from any
1370 old version of Eclipse.</li>
1371 <li>If you had installed additional features and plug-ins into your old
1372 Eclipse, you should re-install them in the new Eclipse.</li>
1373 <li>Start this new version of Eclipse and select
1374 this location using the workspace chooser dialog at startup (or use "<code>-data</code>"
1375 command line argument to pre-select the workspace location).</li>
1377 <h3>Users who do use "-data"</h3>
1378 <p>If you were previously using the "<code>-data</code>" argument to
1379 start Eclipse, your upgrade path is much easier:</p>
1382 <li>Optionally copy your workspace directory to a new, empty location outside of any
1383 Eclipse install directory as a backup.</li>
1384 <li>Install the new version of Eclipse in a new location, separate from any
1385 old versions of Eclipse.</li>
1386 <li>If you had installed additional features and plug-ins into your old
1387 Eclipse, you should re-install them in the new Eclipse.</li>
1388 <li>Start this new version of Eclipse and select this location using the workspace chooser dialog at
1389 startup (or use "<code>-data</code>"
1390 command line argument to pre-select the workspace location).</li>
1392 <p><i>Note:</i> Copying your workspace is recommended because,
1393 after you've upgraded your workspace, you won't be able to use it
1394 again with an older version of Eclipse. If you ever want to go "back in
1395 time" to an earlier release, you will need that backup.</p>
1396 <h3> Users who use User Libraries or classpath containers that contain JARs referencing other libraries via Class-Path in the MANIFEST.MF</h3>
1398 If you want the referenced JAR files to be included in the classpath, you can do one of the following:<br/>
1400 <li>Add the system property (<code>-DresolveReferencedLibrariesForContainers=true</code>) to the <code>-vmargs</code>
1401 list on start-up, or</li>
1402 <li>Manually add the referenced JARs to the User Library or to the project.</li>
1405 <h3>Dropped in bundles may not resolve after upgrade</h3>
1406 <p>If you have installed bundles by dropping them into the <tt>plugins</tt>
1407 or <tt>dropins</tt> directory, they might no longer resolve when you upgrade
1408 to a new Eclipse Platform version. In each new version of the Eclipse Platform,
1409 there are new versions of bundles included in the platform, and often a small
1410 number of removed bundles. This may cause your previously dropped in bundles
1411 to no longer resolve and run. It is always recommended that you install software
1412 via the <tt>Help > Install New Software</tt> mechanism so you are made
1413 aware of any install-time failure to resolve dependencies.
1416 <h2>6. <a name="InteroperabilityWithPreviousReleases">Interoperability with
1417 Previous Releases</a></h2>
1418 <h3>6.1 Interoperability of Release 4.2 with previous releases</h3>
1419 <h4>Sharing projects between heterogeneous Eclipse 4.2 and 3.8</h4>
1420 <p>Special care is required when a project in a team repository is being loaded
1421 and operated on by developers using Eclipse-based products based on different
1422 feature or plug-in versions. The general problem is that the existence,
1423 contents, and interpretation of metadata files in the workspaces may be specific
1424 to a particular feature or plug-in version, and differ between versions. The
1425 workspace compatibility guarantees only cover cases where all developers upgrade
1426 their Eclipse workspaces in lock step. In those cases there should be no problem
1427 with shared metadata. However, when some developers are working in Eclipse 4.2
1428 while others are working in Eclipse 3.x, there are no such guarantees.
1429 This section provides advice for what to do and not to do. It addresses the
1430 specific issues with the Eclipse SDK.</p>
1432 <p>The typical failure mode is noticed by the 4.2 user. 4.2 metadata is lost
1433 when a 3.x user saves changes and then commits the updated metadata files to the
1434 repository. Here's how things typically go awry:</p>
1436 <li>A user working in Eclipse 4.2 creates or modifies a project in a way that
1437 results in changes to a shared metadata file that rely on 4.2-specific
1438 information. The user then commits the updated project files, including the
1439 shared metadata file, to the shared repository.</li>
1440 <li>Another user working in Eclipse 3.x shares this project from the same
1441 repository. The 4.2-specific information in the shared metadata file is not
1442 understood by Eclipse 3.x, and is generally discarded or ignored without
1443 warning. The user modifies the project in a way that results in changes to
1444 the shared metadata file, causing the shared metadata file to be rewritten
1445 without any of the 4.2-specific information. The user commits the updated
1446 project files, including the shared metadata file, to the shared repository.
1447 The user is generally unaware that shared information has just been lost as
1448 a result of their actions.</li>
1449 <li>A user working in Eclipse 4.2 picks up the changes to a project from the
1450 shared repository, including the updated shared metadata file. The user may
1451 be unaware that they have just taken a retrograde step until later when
1452 things start to malfunction.</li>
1454 <p>Here are some things to watch out for when sharing projects between
1455 Eclipse 4.2 and earlier 3.x releases:</p>
1457 <li><b>Virtual folders</b> -
1458 Eclipse 4.2 supports a notion of <i>virtual folders</i> that did not exist
1459 in Eclipse 3.5 or earlier. If such virtual folders are created in 4.2, and the project
1460 is subsequently loaded into an Eclipse 3.5 or earlier workspace, these folders
1461 will not be recognized. Recommendation: avoid creating virtual folders where project
1462 compatibility with Eclipse 3.5 or earlier is required.</li>
1463 <li><b>Resource filters</b> -
1464 Eclipse 4.2 supports a notion of <i>resource filters</i> that did not exist
1465 in Eclipse 3.5 or earlier. If such filters are added to resources in 4.2, and the project
1466 is subsequently loaded into an Eclipse 3.5 or earlier workspace, these filters
1467 will not be recognized. Recommendation: avoid creating resource filters where project
1468 compatibility with Eclipse 3.5 or earlier is required.</li>
1469 <li><b>Predefined path variables</b> -
1470 Eclipse 4.2 supports a set of built in path variables that can be used as the basis
1471 for linked resource locations. Such variables will not be defined automatically in
1472 Eclipse 3.5 or earlier. If compatibility with 3.5 or earlier workspace is required,
1473 users on 3.5 or earlier workspaces will need to define such path variables manually.
1476 <h4>Using Eclipse 4.2 to develop plug-ins that work in Eclipse 3.7</h4>
1477 <p>It is also possible (and reasonable) to use Eclipse 4.2 to develop a plug-in
1478 intended to work in Eclipse 3.7 or earlier. Use the <b>Plug-in Development >
1479 Target Platform </b>preference page to locate non-workspace plug-ins in an Eclipse
1480 3.7 install. This ensures that the code for your plug-in is being compiled and
1481 tested against Eclipse 3.7 APIs, extension points, and plug-ins. (The above
1482 list of concerns do not apply since they affect the layout and interpretation
1483 of files in the plug-in <i>project</i> but none affect the actual deployed form
1484 of the plug-in.)</p>
1487 <p>Sun, Solaris, Java and all Java-based trademarks are trademarks of Oracle Corporation.
1488 in the United States, other countries, or both.</p>
1489 <p>IBM is a trademark of International Business Machines Corporation in the
1490 United States, other countries, or both.</p>
1491 <p>Microsoft, Windows, Windows NT, Vista, and the Windows logo are trademarks of
1492 Microsoft Corporation in the United States, other countries, or both.</p>
1493 <p>Apple and Mac OS are trademarks of Apple Computer, Inc., registered in the
1494 U.S. and other countries.</p>
1495 <p>QNX, Neutrino, and Photon are trademarks or registered trademarks of QNX
1496 Software Systems Ltd.</p>
1497 <p>Other company, product, and service names may be trademarks or service marks
1499 <p>(c) Copyright IBM Corp. and others 2009, 2011</p>
1501 <h2><a name="Appendix1">Appendix 1: Execution Environment by Bundle</a></h2>
1503 <p>In the table below, the "4.1 minimum execution environment"
1504 column indicates the minimum Java class library requirements of each bundle
1505 for the 4.1 release, where the value is one of:</p>
1506 <table border="0" width="90%">
1510 <td align="center"><b>Entry</b></td>
1511 <td align="left"><b>Meaning</b></td>
1514 <td><div align="center"><strong>F1.0</strong></div></td>
1515 <td>J2ME Foundation 1.0 - indicates that the bundle can only be run on
1516 Foundation 1.0 or greater. Note that with the exception of some MicroEdition
1517 IO classes, Foundation 1.0 is a subset of J2SE 1.3.</td>
1520 <td><div align="center"><strong>F1.1</strong></div></td>
1521 <td>J2ME Foundation 1.1 - indicates that the bundle can only be run on
1522 Foundation 1.1 or greater. Note that with the exception of some MicroEdition
1523 IO classes, Foundation 1.1 is a subset of J2SE 1.4.</td>
1526 <td><div align="center"><strong>1.3</strong></div></td>
1527 <td>J2SE 1.3 - indicates that the bundle can only be run on JSE 1.3 or
1531 <td><div align="center"><strong>1.4</strong></div></td>
1532 <td>J2SE 1.4 - indicates that the bundle can only be run on JSE 1.4 or
1536 <td><div align="center"><strong>1.5</strong></div></td>
1537 <td>Java SE 5 - indicates that the bundle can only be run on Java SE 5 or
1542 <td><div align="center"><strong>1.6</strong></div></td>
1543 <td>Java SE 6 - indicates that the bundle can only be run on Java SE 6 or
1547 <td align="center"><b>n/a</b></td>
1548 <td>Unknown at the time of this revision.</td>
1553 <p><b>Table of minimum execution environments by bundle.</b> (See also the
1554 <a href="http://www.eclipse.org/projects/project-plan.php?projectid=rt.equinox#appendix">Equinox Project plan</a>
1555 for the execution environment requirements of bundles contributed via that project.)</p>
1560 <td width="290"><strong>Bundle</strong></td>
1561 <td width="60"><div align="center"><p align="center"><b>4.2<br/>minimum<br/>execution<br/>environment</b></p></div></td>
1564 <td>com.ibm.icu</td>
1565 <td><div align="center">1.5</div></td>
1568 <td>com.jcraft.jsch</td>
1569 <td><div align="center">1.4</div></td>
1573 <td><div align="center">1.5</div></td>
1576 <td>javax.annotation</td>
1577 <td><div align="center">1.5</div></td>
1581 <td><div align="center">1.5</div></td>
1584 <td>javax.inject</td>
1585 <td><div align="center">1.5</div></td>
1588 <td>javax.servlet</td>
1589 <td><div align="center">1.6</div></td>
1592 <td>javax.servlet.jsp</td>
1593 <td><div align="center">1.6</div></td>
1597 <td><div align="center">J2SE-1.2</div></td>
1600 <td>org.apache.ant</td>
1601 <td><div align="center">J2SE-1.2</div></td>
1604 <td>org.apache.batik.css</td>
1605 <td><div align="center">1.3</div></td>
1608 <td>org.apache.batik.util</td>
1609 <td><div align="center">1.3</div></td>
1612 <td>org.apache.batik.util.gui</td>
1613 <td><div align="center">1.3</div></td>
1616 <td>org.apache.commons.codec</td>
1617 <td><div align="center">F1.0</div></td>
1620 <td>org.apache.commons.httpclient</td>
1621 <td><div align="center">F1.0</div></td>
1624 <td>org.apache.commons.logging</td>
1625 <td><div align="center">F1.0</div></td>
1628 <td>org.apache.felix.gogo.command</td>
1629 <td><div align="center">not specified</div></td>
1632 <td>org.apache.felix.gogo.runtime</td>
1633 <td><div align="center">not specified</div></td>
1636 <td>org.apache.felix.gogo.shell</td>
1637 <td><div align="center">not specified</div></td>
1640 <td>org.apache.jasper.glassfish</td>
1641 <td><div align="center">1.6</div></td>
1644 <td>org.apache.lucene</td>
1645 <td><div align="center">1.4</div></td>
1648 <td>org.apache.lucene.analysis</td>
1649 <td><div align="center">1.4</div></td>
1652 <td>org.apache.lucene.core</td>
1653 <td><div align="center">1.4</div></td>
1656 <td>org.eclipse.ant.core</td>
1657 <td><div align="center">1.4</div></td>
1660 <td>org.eclipse.ant.launching</td>
1661 <td><div align="center">1.4</div></td>
1664 <td>org.eclipse.ant.ui</td>
1665 <td><div align="center">1.4</div></td>
1668 <td>org.eclipse.compare</td>
1669 <td><div align="center">1.4</div></td>
1672 <td>org.eclipse.compare.core</td>
1673 <td><div align="center">1.4</div></td>
1676 <td>org.eclipse.compare.win32</td>
1677 <td><div align="center">1.4</div></td>
1680 <td>org.eclipse.core.commands</td>
1681 <td><div align="center">F1.0</div></td>
1684 <td>org.eclipse.core.contenttype</td>
1685 <td><div align="center">F1.0</div></td>
1688 <td>org.eclipse.core.databinding</td>
1689 <td><div align="center">F1.1</div></td>
1692 <td>org.eclipse.core.databinding.beans</td>
1693 <td><div align="center">1.4</div></td>
1696 <td>org.eclipse.core.databinding.observable</td>
1697 <td><div align="center">F1.1</div></td>
1700 <td>org.eclipse.core.databinding.property</td>
1701 <td><div align="center">F1.1</div></td>
1704 <td>org.eclipse.core.expressions</td>
1705 <td><div align="center">F1.0</div></td>
1708 <td>org.eclipse.core.externaltools</td>
1709 <td><div align="center">1.4</div></td>
1712 <td>org.eclipse.core.filebuffers</td>
1713 <td><div align="center">1.4</div></td>
1716 <td>org.eclipse.core.filesystem</td>
1717 <td><div align="center">1.4</div></td>
1720 <td>org.eclipse.core.jobs</td>
1721 <td><div align="center">F1.1</div></td>
1724 <td>org.eclipse.core.net</td>
1725 <td><div align="center">F1.1</div></td>
1728 <td>org.eclipse.core.resources</td>
1729 <td><div align="center">1.5</div></td>
1732 <td>org.eclipse.core.runtime</td>
1733 <td><div align="center">F1.0</div></td>
1736 <td>org.eclipse.core.runtime.compatibility</td>
1737 <td><div align="center">F1.0</div></td>
1740 <td>org.eclipse.core.runtime.compatibility.registry</td>
1741 <td><div align="center">F1.0</div></td>
1744 <td>org.eclipse.core.variables</td>
1745 <td><div align="center">1.4</div></td>
1748 <td>org.eclipse.cvs</td>
1749 <td><div align="center">not specified</div></td>
1752 <td>org.eclipse.debug.core</td>
1753 <td><div align="center">1.4</div></td>
1756 <td>org.eclipse.debug.ui</td>
1757 <td><div align="center">1.4</div></td>
1760 <td>org.eclipse.e4.core.commands</td>
1761 <td><div align="center">1.5</div></td>
1764 <td>org.eclipse.e4.core.contexts</td>
1765 <td><div align="center">1.5</div></td>
1768 <td>org.eclipse.e4.core.di</td>
1769 <td><div align="center">1.5</div></td>
1772 <td>org.eclipse.e4.core.di.extensions</td>
1773 <td><div align="center">1.5</div></td>
1776 <td>org.eclipse.e4.core.services</td>
1777 <td><div align="center">1.5</div></td>
1780 <td>org.eclipse.e4.ui.bindings</td>
1781 <td><div align="center">1.5</div></td>
1784 <td>org.eclipse.e4.ui.css.core</td>
1785 <td><div align="center">1.5</div></td>
1788 <td>org.eclipse.e4.ui.css.swt</td>
1789 <td><div align="center">1.5</div></td>
1792 <td>org.eclipse.e4.ui.css.swt.theme</td>
1793 <td><div align="center">1.5</div></td>
1796 <td>org.eclipse.e4.ui.di</td>
1797 <td><div align="center">1.5</div></td>
1800 <td>org.eclipse.e4.ui.model.workbench</td>
1801 <td><div align="center">1.5</div></td>
1804 <td>org.eclipse.e4.ui.services</td>
1805 <td><div align="center">1.5</div></td>
1808 <td>org.eclipse.e4.ui.widgets</td>
1809 <td><div align="center">1.5</div></td>
1812 <td>org.eclipse.e4.ui.workbench</td>
1813 <td><div align="center">1.5</div></td>
1816 <td>org.eclipse.e4.ui.workbench.addons.swt</td>
1817 <td><div align="center">1.5</div></td>
1820 <td>org.eclipse.e4.ui.workbench.renderers.swt</td>
1821 <td><div align="center">1.5</div></td>
1824 <td>org.eclipse.e4.ui.workbench.swt</td>
1825 <td><div align="center">1.5</div></td>
1828 <td>org.eclipse.e4.ui.workbench3</td>
1829 <td><div align="center">1.5</div></td>
1832 <td>org.eclipse.emf.common</td>
1833 <td><div align="center">1.5</div></td>
1836 <td>org.eclipse.emf.ecore</td>
1837 <td><div align="center">1.5</div></td>
1840 <td>org.eclipse.emf.ecore.change</td>
1841 <td><div align="center">1.5</div></td>
1844 <td>org.eclipse.emf.ecore.xmi</td>
1845 <td><div align="center">1.5</div></td>
1848 <td>org.eclipse.help</td>
1849 <td><div align="center">F1.0</div></td>
1852 <td>org.eclipse.help.base</td>
1853 <td><div align="center">1.5</div></td>
1856 <td>org.eclipse.help.ui</td>
1857 <td><div align="center">1.4</div></td>
1860 <td>org.eclipse.help.webapp</td>
1861 <td><div align="center">1.4</div></td>
1864 <td>org.eclipse.jdt</td>
1865 <td><div align="center">not specified</div></td>
1868 <td>org.eclipse.jdt.annotation</td>
1869 <td><div align="center">1.5</div></td>
1872 <td>org.eclipse.jdt.apt.core</td>
1873 <td><div align="center">1.5</div></td>
1876 <td>org.eclipse.jdt.apt.pluggable.core</td>
1877 <td><div align="center">1.6</div></td>
1880 <td>org.eclipse.jdt.apt.ui</td>
1881 <td><div align="center">1.5</div></td>
1884 <td>org.eclipse.jdt.compiler.apt</td>
1885 <td><div align="center">1.6</div></td>
1888 <td>org.eclipse.jdt.compiler.tool</td>
1889 <td><div align="center">1.6</div></td>
1892 <td>org.eclipse.jdt.core</td>
1893 <td><div align="center">1.4</div></td>
1896 <td>org.eclipse.jdt.core.manipulation</td>
1897 <td><div align="center">1.4</div></td>
1900 <td>org.eclipse.jdt.debug</td>
1901 <td><div align="center">1.5</div></td>
1904 <td>org.eclipse.jdt.debug.ui</td>
1905 <td><div align="center">1.5</div></td>
1908 <td>org.eclipse.jdt.doc.isv</td>
1909 <td><div align="center">not specified</div></td>
1912 <td>org.eclipse.jdt.doc.user</td>
1913 <td><div align="center">not specified</div></td>
1916 <td>org.eclipse.jdt.junit</td>
1917 <td><div align="center">1.5</div></td>
1920 <td>org.eclipse.jdt.junit.core</td>
1921 <td><div align="center">1.4</div></td>
1924 <td>org.eclipse.jdt.junit.runtime</td>
1925 <td><div align="center">1.3</div></td>
1928 <td>org.eclipse.jdt.junit4.runtime</td>
1929 <td><div align="center">1.5</div></td>
1932 <td>org.eclipse.jdt.launching</td>
1933 <td><div align="center">1.5</div></td>
1936 <td>org.eclipse.jdt.ui</td>
1937 <td><div align="center">1.5</div></td>
1940 <td>org.eclipse.jface</td>
1941 <td><div align="center">F1.1</div></td>
1944 <td>org.eclipse.jface.databinding</td>
1945 <td><div align="center">F1.0</div></td>
1948 <td>org.eclipse.jface.text</td>
1949 <td><div align="center">1.4</div></td>
1952 <td>org.eclipse.jsch.core</td>
1953 <td><div align="center">1.4</div></td>
1956 <td>org.eclipse.jsch.ui</td>
1957 <td><div align="center">1.4</div></td>
1960 <td>org.eclipse.ltk.core.refactoring</td>
1961 <td><div align="center">1.4</div></td>
1964 <td>org.eclipse.ltk.ui.refactoring</td>
1965 <td><div align="center">1.4</div></td>
1968 <td>org.eclipse.pde</td>
1969 <td><div align="center">1.4</div></td>
1972 <td>org.eclipse.pde.api.tools</td>
1973 <td><div align="center">1.4</div></td>
1976 <td>org.eclipse.pde.api.tools.ui</td>
1977 <td><div align="center">1.4</div></td>
1980 <td>org.eclipse.pde.build</td>
1981 <td><div align="center">1.4</div></td>
1984 <td>org.eclipse.pde.core</td>
1985 <td><div align="center">1.4</div></td>
1988 <td>org.eclipse.pde.doc.user</td>
1989 <td><div align="center">not specified</div></td>
1992 <td>org.eclipse.pde.ds.core</td>
1993 <td><div align="center">1.4</div></td>
1996 <td>org.eclipse.pde.ds.ui</td>
1997 <td><div align="center">1.4</div></td>
2000 <td>org.eclipse.pde.junit.runtime</td>
2001 <td><div align="center">1.4</div></td>
2004 <td>org.eclipse.pde.launching</td>
2005 <td><div align="center">1.4</div></td>
2008 <td>org.eclipse.pde.runtime</td>
2009 <td><div align="center">1.4</div></td>
2012 <td>org.eclipse.pde.ua.core</td>
2013 <td><div align="center">1.4</div></td>
2016 <td>org.eclipse.pde.ua.ui</td>
2017 <td><div align="center">1.4</div></td>
2020 <td>org.eclipse.pde.ui</td>
2021 <td><div align="center">1.4</div></td>
2024 <td>org.eclipse.pde.ui.templates</td>
2025 <td><div align="center">1.4</div></td>
2028 <td>org.eclipse.platform</td>
2029 <td><div align="center">F1.0</div></td>
2032 <td>org.eclipse.platform.doc.isv</td>
2033 <td><div align="center">not specified</div></td>
2036 <td>org.eclipse.platform.doc.user</td>
2037 <td><div align="center">not specified</div></td>
2040 <td>org.eclipse.rcp</td>
2041 <td><div align="center">not specified</div></td>
2044 <td>org.eclipse.sdk</td>
2045 <td><div align="center">not specified</div></td>
2048 <td>org.eclipse.search</td>
2049 <td><div align="center">1.4</div></td>
2052 <td>org.eclipse.swt</td>
2053 <td><div align="center">F1.0</div></td>
2056 <td>org.eclipse.team.core</td>
2057 <td><div align="center">1.4</div></td>
2060 <td>org.eclipse.team.cvs.core</td>
2061 <td><div align="center">1.4</div></td>
2064 <td>org.eclipse.team.cvs.ssh2</td>
2065 <td><div align="center">1.4</div></td>
2068 <td>org.eclipse.team.cvs.ui</td>
2069 <td><div align="center">1.4</div></td>
2072 <td>org.eclipse.team.ui</td>
2073 <td><div align="center">1.4</div></td>
2076 <td>org.eclipse.text</td>
2077 <td><div align="center">1.4</div></td>
2080 <td>org.eclipse.ui</td>
2081 <td><div align="center">F1.0</div></td>
2084 <td>org.eclipse.ui.browser</td>
2085 <td><div align="center">1.5</div></td>
2088 <td>org.eclipse.ui.cheatsheets</td>
2089 <td><div align="center">1.4</div></td>
2092 <td>org.eclipse.ui.console</td>
2093 <td><div align="center">1.4</div></td>
2096 <td>org.eclipse.ui.editors</td>
2097 <td><div align="center">1.4</div></td>
2100 <td>org.eclipse.ui.externaltools</td>
2101 <td><div align="center">1.4</div></td>
2104 <td>org.eclipse.ui.forms</td>
2105 <td><div align="center">1.4</div></td>
2108 <td>org.eclipse.ui.ide</td>
2109 <td><div align="center">1.4</div></td>
2112 <td>org.eclipse.ui.ide.application</td>
2113 <td><div align="center">1.4</div></td>
2116 <td>org.eclipse.ui.intro</td>
2117 <td><div align="center">1.4</div></td>
2120 <td>org.eclipse.ui.intro.universal</td>
2121 <td><div align="center">1.4</div></td>
2124 <td>org.eclipse.ui.navigator</td>
2125 <td><div align="center">1.4</div></td>
2128 <td>org.eclipse.ui.navigator.resources</td>
2129 <td><div align="center">1.4</div></td>
2132 <td>org.eclipse.ui.net</td>
2133 <td><div align="center">F1.1</div></td>
2136 <td>org.eclipse.ui.trace</td>
2137 <td><div align="center">1.5</div></td>
2140 <td>org.eclipse.ui.views</td>
2141 <td><div align="center">1.4</div></td>
2144 <td>org.eclipse.ui.views.log</td>
2145 <td><div align="center">1.4</div></td>
2148 <td>org.eclipse.ui.views.properties.tabbed</td>
2149 <td><div align="center">F1.0</div></td>
2152 <td>org.eclipse.ui.win32</td>
2153 <td><div align="center">1.4</div></td>
2156 <td>org.eclipse.ui.workbench</td>
2157 <td><div align="center">1.5</div></td>
2160 <td>org.eclipse.ui.workbench.texteditor</td>
2161 <td><div align="center">1.4</div></td>
2164 <td>org.eclipse.update.configurator</td>
2165 <td><div align="center">F1.0</div></td>
2168 <td>org.hamcrest.core</td>
2169 <td><div align="center">1.5</div></td>
2173 <td><div align="center">1.3</div></td>
2177 <td><div align="center">1.5</div></td>
2180 <td>org.objectweb.asm</td>
2181 <td><div align="center">1.3</div></td>
2184 <td>org.slf4j.api</td>
2185 <td><div align="center">F1.1</div></td>
2188 <td>org.w3c.css.sac</td>
2189 <td><div align="center">F1.0</div></td>
2192 <td>org.w3c.dom.smil</td>
2193 <td><div align="center">F1.0</div></td>
2196 <td>org.w3c.dom.svg</td>
2197 <td><div align="center">F1.0</div></td>
OSDN Git Service
