diff options
| author | David Williams | 2016-05-30 17:25:09 +0000 |
|---|---|---|
| committer | David Williams | 2016-05-30 17:25:09 +0000 |
| commit | 16d10bdf870d6000e219039a840715f5cc2a5859 (patch) | |
| tree | cba8e1590e5aa81a756e5030ea29ba44994e0d12 | |
| parent | 5ad14dc0fda45d4fbbc56b9db784821ec2af2050 (diff) | |
| download | eclipse.platform.releng-16d10bdf870d6000e219039a840715f5cc2a5859.tar.gz eclipse.platform.releng-16d10bdf870d6000e219039a840715f5cc2a5859.tar.xz eclipse.platform.releng-16d10bdf870d6000e219039a840715f5cc2a5859.zip | |
493368 latest matching "website" versionI20160601-1000I20160531-2330I20160531-2000I20160530-2000
Change-Id: I63accde59c7550dcb5d2d62ed3a9bcc61f083811
| -rw-r--r-- | features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html | 891 |
1 files changed, 388 insertions, 503 deletions
diff --git a/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html b/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html index a43e78ef..3e64d0ba 100644 --- a/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html +++ b/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html @@ -1,13 +1,18 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> <head> - <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>Eclipse Project Release Notes 4.6 (Neon)</title> </head> +<!-- Please validate as "xhtml1 strict", at +https://validator.w3.org/check?uri=http%3A%2F%2Fwww.eclipse.org%2Feclipse%2Fdevelopment%2Freadme_eclipse_4.6.html;ss=1 +(It must be "on website" to validte.) +--> <body> -<h1><a class="mozTocH1" name="mozTocId414824"></a>Eclipse Project -Release Notes</h1> -<p> Release 4.6.0 (Neon)<br> -Last revised May 23, 2016 </p> +<h1><a class="mozTocH1" name="mozTocId299852" />Eclipse Project Release +Notes</h1> +<p>Release 4.6.0 (Neon)</p> +<p>Last revised May 30, 2016</p> <!-- This folling link to www.eclipse.org should be commented out or removed in final version of the @@ -21,277 +26,257 @@ after the release. Release Notes 4.6 (Neon)</a>. There may or may not be changes made after the product is released. You can tell by checking the "last revised" date near the top of this page. </p> -<p style="text-align: left;"> <strong>This software is OSI Certified -Open Source Software.<br> -OSI Certified is a certification mark of the Open Source -Initiative. </strong> </p> +<p style="text-align: left; font-weight: bold;"> This software is OSI +Certified Open Source Software.<br /> +OSI Certified is a certification mark of the Open Source Initiative. </p> +<h2 id="TargetOperatingEnvironments1"><a class="mozTocH2" + name="mozTocId438134" /></h2> <ol id="mozToc"> -<!--mozToc h1 1 h2 2 h3 3 h4 4--> - <li><a href="#mozTocId414824">Eclipse Project Release Notes</a> +<!--mozToc h1 1 h2 2 h3 3 h4 4 h5 5 h6 6--> + <li><a href="#mozTocId299852">Eclipse Project Release Notes</a> <ol> - <li><a href="#mozTocId637925"></a></li> - <li><a href="#mozTocId311932">Target Operating Environments</a></li> - <li><a href="#mozTocId356713">Compatibility with Previous Releases</a> + <li><a href="#mozTocId438134">Target Operating Environments</a></li> + <li><a href="#mozTocId569479">Compatibility with Previous Releases</a> <ol> - <li><a href="#mozTocId760552">Compatibility of Release 4.6 + <li><a href="#mozTocId324309">Compatibility of Release 4.6 with 4.5</a></li> </ol> </li> - <li><a href="#mozTocId528410">Known Issues</a> + <li><a href="#mozTocId214943">Known Issues</a> <ol> - <li><a href="#mozTocId31587">General problems</a></li> - <li><a href="#mozTocId76441">General - Startup</a> + <li><a href="#mozTocId758150">General problems</a></li> + <li><a href="#mozTocId559320">General - Startup</a> <ol> - <li><a href="#mozTocId178265">Installation/Configuration + <li><a href="#mozTocId693657">Installation/Configuration issues that can cause Eclipse to fail start</a></li> - <li><a href="#mozTocId229730"> Invalid characters in + <li><a href="#mozTocId337416"> Invalid characters in install directory prevents Eclipse from starting </a></li> - <li><a href="#mozTocId662536">Hanging during class + <li><a href="#mozTocId639565">Hanging during class loading when out of permanent generation memory</a></li> </ol> </li> - <li><a href="#mozTocId710344">General - GCJ</a> + <li><a href="#mozTocId148479">General - GCJ</a> <ol> - <li><a href="#mozTocId3915">Problems with classloaders in -created threads</a></li> - <li><a href="#mozTocId590607">Deadlock creating + <li><a href="#mozTocId584602">Problems with classloaders +in created threads</a></li> + <li><a href="#mozTocId403443">Deadlock creating executable extension in Plugin.startup</a></li> - <li><a href="#mozTocId148431">Potential Problems + <li><a href="#mozTocId984286">Potential Problems Converting Plug-in Manifests</a></li> - <li><a href="#mozTocId544740">Location for Debug Options + <li><a href="#mozTocId993987">Location for Debug Options File on Mac OS</a></li> - <li><a href="#mozTocId341887">Issues with JNI that use + <li><a href="#mozTocId808188">Issues with JNI that use FindClass</a></li> </ol> </li> - <li><a href="#mozTocId961605">Platform - Ant</a> + <li><a href="#mozTocId324774">Platform - Ant</a> <ol> - <li><a href="#mozTocId442280">Custom Ant tasks and Ant + <li><a href="#mozTocId480194">Custom Ant tasks and Ant types must be separate from plug-in library JARs</a></li> - <li><a href="#mozTocId755617">XDoclet support from within + <li><a href="#mozTocId912215">XDoclet support from within Eclipse</a></li> - <li><a href="#mozTocId954641">Ant Editor code completion + <li><a href="#mozTocId31051">Ant Editor code completion based on Ant 1.6.x</a></li> - <li><a href="#mozTocId260211">Setting build loggers not + <li><a href="#mozTocId925603">Setting build loggers not supported when debugging Ant builds</a></li> - <li><a href="#mozTocId642196">Renaming an External Tool + <li><a href="#mozTocId669417">Renaming an External Tool builder set to run during auto-build will cause errors</a></li> - <li><a href="#mozTocId375822">Slow typing/saving of the + <li><a href="#mozTocId772119">Slow typing/saving of the Ant editor with imports that define numerous macrodefs</a></li> - <li><a href="#mozTocId525690">Ant 1.8.x reports missing + <li><a href="#mozTocId715004">Ant 1.8.x reports missing libraries as build failures</a></li> </ol> </li> - <li><a href="#mozTocId1352">Platform - User Assistance</a> + <li><a href="#mozTocId876322">Platform - User Assistance</a> <ol> - <li><a href="#mozTocId983547">Welcome page not displayed + <li><a href="#mozTocId828477">Welcome page not displayed properly (Linux/Unix)</a></li> - <li><a href="#mozTocId549237">Help browser tool bar + <li><a href="#mozTocId26110">Help browser tool bar buttons do not work for some documents</a></li> - <li><a href="#mozTocId705626">Help documents not + <li><a href="#mozTocId324012">Help documents not displayed in a browser or very slow document loading (Windows only)</a></li> - <li><a href="#mozTocId139783">Working disconnected from + <li><a href="#mozTocId227368">Working disconnected from the network (Windows only)</a></li> - <li><a href="#mozTocId519549">Using Internet Explorer in + <li><a href="#mozTocId121403">Using Internet Explorer in offline mode (Windows only)</a></li> </ol> </li> - <li><a href="#mozTocId516525">Platform - UI</a> + <li><a href="#mozTocId683637">Platform - UI</a> <ol> - <li><a href="#mozTocId828423">Dirty state not tracked + <li><a href="#mozTocId348035">Dirty state not tracked properly for OLE documents (Windows only)</a></li> - <li><a href="#mozTocId212451">OLE document crashes can + <li><a href="#mozTocId878052">OLE document crashes can cause Eclipse to also crash (Windows only)</a></li> - <li><a href="#mozTocId190553">Toolbars only containing + <li><a href="#mozTocId452707">Toolbars only containing contributed controls exhibit display errors on Mac/Linux</a></li> - <li><a href="#mozTocId434307">Capabilities and Activities + <li><a href="#mozTocId443682">Allocating enough memory +and solving OutOfMemoryError</a></li> + <li><a href="#mozTocId862142">Capabilities and Activities don't affect the menus and toolbars</a></li> </ol> </li> - <li><a href="#mozTocId694051">Platform - SWT</a> + <li><a href="#mozTocId554478">Platform - SWT</a> <ol> - <li><a href="#mozTocId191730">SWT Browser widget crashes + <li><a href="#mozTocId69222">Eclipse plug-in based on the +SWT Browser throws exception</a></li> + <li><a href="#mozTocId519796">SWT Browser widget crashes when run with XULRunner 31 run-time (Linux only)</a></li> - <li><a href="#mozTocId381643">Download progress window -not shown with XULRunner 31 run-time</a></li> - <li><a href="#mozTocId568065">Eclipse crashes randomly -when using the Webkit based browser on RHEL 6.5</a></li> - <li><a href="#mozTocId353468">Eclipse plug-in based on -the SWT Browser throws exception</a></li> - <li><a href="#mozTocId664550">Table background is not -painted correctly when SWT.EraseItem is used (specific versions of GTK3)</a></li> - <li><a href="#mozTocId998858">TreeItems with decorated -icons overwrite text with Eclipse dark theme on GTK+ 3.10 and above</a></li> - <li><a href="#mozTocId618828">Some keybindings/shortcuts -become unresponsive (GTK3 only)</a></li> - <li><a href="#mozTocId403331">Eclipse crashes with GTK+ 2 -and Oxygen-gtk2 theme under KDE desktop</a></li> - <li><a href="#mozTocId437801">Eclipse hangs when pasting -from an unresponsive application (GTK only)</a></li> - <li><a href="#mozTocId556263">IME conversion problem + <li><a href="#mozTocId664509">IME conversion problem (Solaris GTK only)</a></li> - <li><a href="#mozTocId944641">Eclipse won't start (Linux + <li><a href="#mozTocId516202">Eclipse won't start (Linux GTK PPC only)</a></li> - <li><a href="#mozTocId900336">Older versions of some -Windows screen readers no longer work with Eclipse</a></li> - <li><a href="#mozTocId436984">Menu on TaskItem doesn't -work for an SWT application when AppName is not set on Windows</a></li> - <li><a href="#mozTocId759240">Eclipse icon is duplicated + <li><a href="#mozTocId238090">Eclipse icon is duplicated in task-bar on Windows</a></li> - <li><a href="#mozTocId220079">BIDI Segments in Text + <li><a href="#mozTocId414883">BIDI Segments in Text controls</a></li> - <li><a href="#mozTocId638859">Block Selection + <li><a href="#mozTocId518357">Block Selection functionality provided by StyledText is not BIDI aware</a></li> </ol> </li> - <li><a href="#mozTocId812923">Platform - Team - CVS</a> + <li><a href="#mozTocId263012">Platform - Team - CVS</a> <ol> - <li><a href="#mozTocId593797">CVS server compatibility</a></li> - <li><a href="#mozTocId640505">Connection cannot be found + <li><a href="#mozTocId262771">CVS server compatibility</a></li> + <li><a href="#mozTocId532855">Connection cannot be found after initially missing</a></li> - <li><a href="#mozTocId200631">"Received broken pipe + <li><a href="#mozTocId660590">Received broken pipe signal" error from server</a></li> - <li><a href="#mozTocId500486">"Terminated with fatal + <li><a href="#mozTocId971246">Terminated with fatal signal 10" error from server</a></li> - <li><a href="#mozTocId987364">"Unknown response" error -using ext connection method</a></li> - <li><a href="#mozTocId122538">A disabled CVS capability + <li><a href="#mozTocId689776">error using ext connection +method</a></li> + <li><a href="#mozTocId50418">A disabled CVS capability may not be auto-enabled in existing workspaces</a></li> - <li><a href="#mozTocId881444">Builder output files may + <li><a href="#mozTocId533799">Builder output files may appear as changed</a></li> - <li><a href="#mozTocId83566">Enabling GNOME proxy support</a></li> + <li><a href="#mozTocId253283">Enabling GNOME proxy support</a></li> </ol> </li> - <li><a href="#mozTocId693443">Platform - Install/Update</a> + <li><a href="#mozTocId805874">Platform - Install/Update</a> <ol> - <li><a href="#mozTocId78143">Manually installing features -and plug-ins on a FAT file system (Windows only)</a></li> - <li><a href="#mozTocId327444">Connecting to untrusted + <li><a href="#mozTocId914600">Manually installing +features and plug-ins on a FAT file system (Windows only)</a></li> + <li><a href="#mozTocId648565">Connecting to untrusted sites using https</a></li> - <li><a href="#mozTocId712235">Extension location is lost + <li><a href="#mozTocId104394">Extension location is lost if the install path changes</a></li> </ol> </li> - <li><a href="#mozTocId170641">Java development tools (JDT)</a> + <li><a href="#mozTocId428861">Java development tools (JDT)</a> <ol> - <li><a href="#mozTocId246992">Multiple regions formatting + <li><a href="#mozTocId180305">Multiple regions formatting in a given source snippet</a></li> - <li><a href="#mozTocId472358">Searching for constant + <li><a href="#mozTocId589358">Searching for constant field references</a></li> - <li><a href="#mozTocId990768">Cut, copy, paste not + <li><a href="#mozTocId577868">Cut, copy, paste not working for linked resources in views showing Java elements</a></li> - <li><a href="#mozTocId876065">Java working sets not + <li><a href="#mozTocId554543">Java working sets not working correctly for elements from JRE system library container</a></li> - <li><a href="#mozTocId760232">Breakpoints unreliable + <li><a href="#mozTocId157019">Breakpoints unreliable running Sun 1.6.0_14</a></li> - <li><a href="#mozTocId157025">Suspend on uncaught + <li><a href="#mozTocId440090">Suspend on uncaught exception overrides exception breakpoint location filters</a></li> - <li><a href="#mozTocId209402">Running Java programs with + <li><a href="#mozTocId812347">Running Java programs with non-Latin-1 characters in package or class names</a></li> - <li><a href="#mozTocId573670">Cannot run or debug class + <li><a href="#mozTocId638407">Cannot run or debug class in a project with GB18030 characters in project name</a></li> - <li><a href="#mozTocId78501">Cannot detect installed JRE + <li><a href="#mozTocId994970">Cannot detect installed JRE with GB18030 characters in path name</a></li> - <li><a href="#mozTocId633891">Cannot generate Javadoc for + <li><a href="#mozTocId324283">Cannot generate Javadoc for packages with GB18030 characters in the name</a></li> - <li><a href="#mozTocId27992">Unable to debug stack + <li><a href="#mozTocId524553">Unable to debug stack overflows</a></li> - <li><a href="#mozTocId970095">Evaluation limitation</a></li> - <li><a href="#mozTocId698026">Missing debug attributes</a></li> - <li><a href="#mozTocId11693">Using Hot Code Replace</a></li> - <li><a href="#mozTocId736358">Scrapbook</a></li> - <li><a href="#mozTocId233701">Debugging over slow + <li><a href="#mozTocId162517">Evaluation limitation</a></li> + <li><a href="#mozTocId408387">Missing debug attributes</a></li> + <li><a href="#mozTocId330034">Using Hot Code Replace</a></li> + <li><a href="#mozTocId976120">Scrapbook</a></li> + <li><a href="#mozTocId666507">Debugging over slow connections</a></li> - <li><a href="#mozTocId550867">Updating of inspected values</a></li> - <li><a href="#mozTocId579316">Stepping over native + <li><a href="#mozTocId207158">Updating of inspected values</a></li> + <li><a href="#mozTocId821393">Stepping over native methods that perform I/O</a></li> - <li><a href="#mozTocId513966">VM and process termination + <li><a href="#mozTocId724969">VM and process termination running on IBM 1.3 JVM on Linux (Linux only)</a></li> - <li><a href="#mozTocId726887">Java Annotation Processing</a></li> - <li><a href="#mozTocId838822">Java indexing encounters + <li><a href="#mozTocId606104">Java Annotation Processing</a></li> + <li><a href="#mozTocId188069">Java indexing encounters problems when a folder is used both as a source and a class folder</a></li> </ol> </li> - <li><a href="#mozTocId862851">Plug-in Development Environment + <li><a href="#mozTocId25456">Plug-in Development Environment (PDE)</a> <ol> - <li><a href="#mozTocId690680">Feature manifest editor + <li><a href="#mozTocId179699">Feature manifest editor does not preserve all comments</a></li> - <li><a href="#mozTocId587493">PDE will not unzip source + <li><a href="#mozTocId243421">PDE will not unzip source zips of some plug-ins</a></li> - <li><a href="#mozTocId635267">Emacs key bindings do not + <li><a href="#mozTocId722932">Emacs key bindings do not work in manifest editor fields</a></li> - <li><a href="#mozTocId216192">Export of plug-in may + <li><a href="#mozTocId828449">Export of plug-in may silently drop classes</a></li> - <li><a href="#mozTocId870661">Compilation errors when + <li><a href="#mozTocId89714">Compilation errors when exporting projects not stored outside of the workspace</a></li> - <li><a href="#mozTocId631939">Headless build needs to be + <li><a href="#mozTocId270371">Headless build needs to be run from a fully qualified path</a></li> - <li><a href="#mozTocId965166">Importing in Eclipse + <li><a href="#mozTocId73293">Importing in Eclipse application fails if plug-in exists in host workspace</a></li> - <li><a href="#mozTocId723029">Reusing a workspace after + <li><a href="#mozTocId914239">Reusing a workspace after changing architectures silently breaks PDE models</a></li> - <li><a href="#mozTocId923139">Missing @since tag API + <li><a href="#mozTocId624312">Missing @since tag API Tools problems on interface fields containing @noreference tag</a></li> </ol> </li> </ol> </li> - <li><a href="#mozTocId420991">Running Eclipse</a> + <li><a href="#mozTocId19817">Running Eclipse</a> <ol> - <li><a href="#mozTocId230700">Allocating enough memory and + <li><a href="#mozTocId60052">Allocating enough memory and solving OutOfMemoryErrors</a></li> - <li><a href="#mozTocId196879">Selecting a workspace</a></li> - <li><a href="#mozTocId266563">Specifying the Java virtual + <li><a href="#mozTocId735187">Selecting a workspace</a></li> + <li><a href="#mozTocId620725">Specifying the Java virtual machine</a></li> - <li><a href="#mozTocId228378">Mac OS X</a></li> - <li><a href="#mozTocId788467">Shared Install</a></li> - <li><a href="#mozTocId105865">Special Operating System + <li><a href="#mozTocId928700">Mac OS X</a></li> + <li><a href="#mozTocId221199">Shared Install</a></li> + <li><a href="#mozTocId317919">Special Operating System Requirements</a> <ol> - <li><a href="#mozTocId576803">AIX</a></li> - <li><a href="#mozTocId83227">HPUX</a></li> - <li><a href="#mozTocId203915">Solaris</a></li> + <li><a href="#mozTocId914102">AIX</a></li> + <li><a href="#mozTocId383156">HPUX</a></li> + <li><a href="#mozTocId2011">Solaris</a></li> </ol> </li> </ol> </li> - <li><a href="#mozTocId320201">Upgrading Workspace from a Previous + <li><a href="#mozTocId575572">Upgrading Workspace from a Previous Release</a> <ol> - <li><a href="#mozTocId35396">Users who don't use "-data"</a></li> - <li><a href="#mozTocId19126">Users who do use "-data"</a></li> - <li><a href="#mozTocId209647">Users who use User Libraries or + <li><a href="#mozTocId401691">Users who don't use "-data"</a></li> + <li><a href="#mozTocId197750">Users who do use "-data"</a></li> + <li><a href="#mozTocId839433">Users who use User Libraries or classpath containers that contain JARs referencing other libraries via Class-Path in the MANIFEST.MF</a></li> - <li><a href="#mozTocId682919">Dropped in bundles may not + <li><a href="#mozTocId623237">Dropped in bundles may not resolve after upgrade</a></li> </ol> </li> - <li><a href="#mozTocId500419">Interoperability with Previous + <li><a href="#mozTocId638978">Interoperability with Previous Releases</a> <ol> - <li><a href="#mozTocId155846">Interoperability of Release 4.6 + <li><a href="#mozTocId759237">Interoperability of Release 4.6 with previous releases</a> <ol> - <li><a href="#mozTocId676468">Sharing projects between + <li><a href="#mozTocId226004">Sharing projects between heterogeneous Eclipse 4.6 and 4.5</a></li> - <li><a href="#mozTocId538141">Using Eclipse 4.6 to + <li><a href="#mozTocId574781">Using Eclipse 4.6 to develop plug-ins that work in Eclipse 4.5</a></li> </ol> </li> </ol> </li> - <li><a href="#mozTocId530462">Appendix: Execution Environment by + <li><a href="#mozTocId317294">Appendix: Execution Environment by Bundle</a></li> </ol> </li> </ol> -<h2 id="TargetOperatingEnvironments"><a class="mozTocH2" - name="mozTocId637925"></a><br> -</h2> -<h2 id="TargetOperatingEnvironments"><a class="mozTocH2" - name="mozTocId311932"></a>Target Operating Environments</h2> +<h2 id="TargetOperatingEnvironments2">Target Operating Environments</h2> <p>In order to remain current, each Eclipse Project release targets reasonably current operating environments.</p> <p>Most of the Eclipse SDK is "pure" Java code and has no direct @@ -331,44 +316,44 @@ all reference platforms.</p> <p>The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard, on Windows, Linux and the Macintosh.</p> <p>German and Japanese locales are tested.</p> -<h2 id="Compatibility"><a class="mozTocH2" name="mozTocId356713"></a>Compatibility +<h2 id="Compatibility"><a class="mozTocH2" name="mozTocId569479" />Compatibility with Previous Releases</h2> -<h3><a class="mozTocH3" name="mozTocId760552"></a>Compatibility of +<h3><a class="mozTocH3" name="mozTocId324309" />Compatibility of Release 4.6 with 4.5</h3> <p>Eclipse 4.6 is compatible with Eclipse 4.5 (and all earlier 3.x versions).</p> <p> <strong>API Contract Compatibility:</strong> Eclipse SDK 4.6 is upwards contract-compatible with Eclipse SDK 4.5 except in those areas noted in the <a - href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_6_porting_guide.html" - target="_top"> <em>Eclipse 4.6 Plug-in Migration Guide</em> </a>. -Programs that use affected APIs and extension points will need to be -ported to Eclipse SDK 4.6 APIs. Downward contract compatibility is not -supported. There is no guarantee that compliance with Eclipse SDK 4.6 -APIs would ensure compliance with Eclipse SDK 4.5 APIs. Refer to <a - href="https://wiki.eclipse.org/Evolving_Java-based_APIs"> <em>Evolving -Java-based APIs</em> </a> for a discussion of the kinds of API changes + href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_6_porting_guide.html"><em>Eclipse +4.6 Plug-in Migration Guide</em></a>. Programs that use affected APIs +and extension points will need to be ported to Eclipse SDK 4.6 APIs. +Downward contract compatibility is not supported. There is no guarantee +that compliance with Eclipse SDK 4.6 APIs would ensure compliance with +Eclipse SDK 4.5 APIs. Refer to <a + href="https://wiki.eclipse.org/Evolving_Java-based_APIs"><em>Evolving +Java-based APIs</em></a> for a discussion of the kinds of API changes that maintain contract compatibility. </p> <p> <strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 4.6 is upwards binary-compatible with Eclipse SDK 4.5 except in those areas noted in the <a - href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_6_porting_guide.html" - target="_top"> <em>Eclipse 4.6 Plug-in Migration Guide</em> </a>. -Downward plug-in compatibility is not supported. Plug-ins for Eclipse -SDK 4.6 will not be usable in Eclipse SDK 4.5. Refer to <a + href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_6_porting_guide.html"><em>Eclipse +4.6 Plug-in Migration Guide</em> </a>. Downward plug-in compatibility +is not supported. Plug-ins for Eclipse SDK 4.6 will not be usable in +Eclipse SDK 4.5. Refer to <a href="https://wiki.eclipse.org/Evolving_Java-based_APIs"> <em>Evolving -Java-based APIs</em> </a> for a discussion of the kinds of API changes +Java-based APIs</em></a> for a discussion of the kinds of API changes that maintain binary compatibility. </p> <p> <strong>Source Compatibility:</strong> Eclipse SDK 4.6 is upwards source-compatible with Eclipse SDK 4.5 except in the areas noted in the <a - href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_6_porting_guide.html" - target="_top"> <em>Eclipse 4.6 Plug-in Migration Guide</em> </a>. -This means that source files written to use Eclipse SDK 4.5 APIs might -successfully compile and run against Eclipse SDK 4.6 APIs, although -this is not guaranteed. Downward source compatibility is not supported. -If source files use new Eclipse SDK APIs, they will not be usable with -an earlier version of the Eclipse SDK. </p> + href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_6_porting_guide.html"><em>Eclipse +4.6 Plug-in Migration Guide</em> </a>. This means that source files +written to use Eclipse SDK 4.5 APIs might successfully compile and run +against Eclipse SDK 4.6 APIs, although this is not guaranteed. Downward +source compatibility is not supported. If source files use new Eclipse +SDK APIs, they will not be usable with an earlier version of the +Eclipse SDK. </p> <p> <strong>Workspace Compatibility:</strong> Eclipse SDK 4.6 is upwards workspace-compatible with earlier 3.x and 4.x versions of the Eclipse SDK unless noted. This means that workspaces and projects @@ -398,17 +383,17 @@ are inherently unsupportable and receive no guarantees about compatibility within a single release much less with earlier releases. Refer to <a href="https://www.eclipse.org/articles/Article-API-Use/index.html"> <em>How -to Use the Eclipse API</em> </a> for information about how to write +to Use the Eclipse API</em></a> for information about how to write compliant plug-ins. </p> -<h2 id="KnownIssues"><a class="mozTocH2" name="mozTocId528410"></a>Known +<h2 id="KnownIssues"><a class="mozTocH2" name="mozTocId214943" />Known Issues</h2> <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> -<h3 id="I-General"><a class="mozTocH3" name="mozTocId31587"></a>General +<h3 id="I-General"><a class="mozTocH3" name="mozTocId758150" />General problems</h3> -<h3 id="I-General-Startup"><a class="mozTocH3" name="mozTocId76441"></a>General +<h3 id="I-General-Startup"><a class="mozTocH3" name="mozTocId559320" />General - Startup</h3> -<h4><a class="mozTocH4" name="mozTocId178265"></a>Installation/Configuration +<h4><a class="mozTocH4" name="mozTocId693657" />Installation/Configuration issues that can cause Eclipse to fail start</h4> <p>Here are some common problems that can cause Eclipse not to start:</p> <ul> @@ -421,7 +406,7 @@ also the <a href="#RunningEclipse">Running Eclipse</a> section below.) <li>Running Eclipse on Gentoo Linux may result in the following error message: <div style="margin-left: 40px;"> <code> * run-java-tool is not -available for sun-jdk-1.6 on i686<br> +available for sun-jdk-1.6 on i686<br /> * IMPORTANT: some Java tools are not available on some VMs on some architectures </code> </div> If this occurs, start Eclipse by specifying a -vm argument, either @@ -448,8 +433,8 @@ problem set their configuration area explicitly using the <code>-configuration</ command line argument. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=67719">67719</a>) </li> </ul> -<h4><a class="mozTocH4" name="mozTocId229730"></a> <b>Invalid -characters in install directory prevents Eclipse from starting</b> </h4> +<h4><a class="mozTocH4" name="mozTocId337416" /> <b>Invalid characters +in install directory prevents Eclipse from starting</b> </h4> <p> Eclipse will fail to launch if installed in a directory whose path contains certain invalid characters, including :%#<>"!. The workaround is to install Eclipse in a directory whose path does not @@ -457,14 +442,14 @@ contain invalid characters. (bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=3109">3109</a> and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=17281">17281</a>) </p> -<h4><a class="mozTocH4" name="mozTocId662536"></a>Hanging during class +<h4><a class="mozTocH4" name="mozTocId639565" />Hanging during class loading when out of permanent generation memory</h4> <p> The Oracle JVM may hang indefinitely during class loading if it runs out of permanent generation memory. This will cause CPU usage to stay at 100% until the process is ended. See the section <a href="#RunningEclipse">Running Eclipse</a> for details on addressing this VM problem. </p> -<h3 id="I-General-GCJ"><a class="mozTocH3" name="mozTocId710344"></a>General +<h3 id="I-General-GCJ"><a class="mozTocH3" name="mozTocId148479" />General - GCJ</h3> <p>GCJ is an effort by the GCC team to provide an open source Java compiler and runtime environment to interpret Java bytecode. @@ -477,11 +462,11 @@ is often tested on by Eclipse developers.</p> org.eclipse.core.runtime.Plugin' that can be found in the logs (located in workspace/.metadata/.log)</li> </ul> -<p>The workspace's log file is a good place to check to identify +<p> The workspace's log file is a good place to check to identify whether GCJ is being used or not. Every Eclipse log session is prepended with information about the runtime environment that was used -to run Eclipse. The log may include something like the following:</p> -<code>java.fullversion=GNU libgcj 4.2.1 (Debian 4.2.1-5)</code> +to run Eclipse. The log may include something like the following: <code>java.fullversion=GNU +libgcj 4.2.1 (Debian 4.2.1-5)</code> </p> <p> If Eclipse does start, one can check which runtime environment is being used to run Eclipse by going to <b>Help > About Eclipse SDK > Installation Details > Configuration</b>. The <b>About</b> @@ -489,8 +474,9 @@ dialog itself can also provide other information, the build identifier can be of particular interest as it is tagged by some distributions. This allows the user to identify whether Eclipse was downloaded through the distribution's package management system or directly from the -eclipse.org web site. </p> -Eg: <code>Build id: M20070212-1330 (Ubuntu version: 3.2.2-0ubuntu3)</code> +eclipse.org web site. <br /> +Such as:<br /> +<code>Build id: M20070212-1330 (Ubuntu version: 3.2.2-0ubuntu3)</code> </p> <p>The two most common workarounds are:</p> <ul> <li>download the Eclipse binary from eclipse.org directly</li> @@ -501,38 +487,39 @@ Eg: <code>Build id: M20070212-1330 (Ubuntu version: 3.2.2-0ubuntu3)</code> <li><a href="http://www.eclipse.org/downloads/">http://www.eclipse.org/downloads/</a></li> <li><a href="http://download.eclipse.org/eclipse/downloads/">http://download.eclipse.org/eclipse/downloads/</a></li> </ul> -It is imperative that 64-bit builds are downloaded and used if a 64-bit -Java runtime environment has been installed. Below are two sample -tarball names of version 4.6 of the Eclipse SDK packaged for 32-bit and -64-bit processors. -<pre>eclipse-SDK-4.6-linux-gtk.tar.gz (32-bit)<br>eclipse-SDK-4.6-linux-gtk-x86_64.tar.gz (64-bit)</pre> -<p>To run Eclipse with an alternate Java runtime environment, the path +<p> It is imperative that 64-bit builds are downloaded and used if a +64-bit Java runtime environment has been installed. Below are two +sample tarball names of version 4.6 of the Eclipse SDK packaged for +32-bit and 64-bit processors.<br /> +<code>eclipse-SDK-4.6-linux-gtk.tar.gz (32-bit)</code><br /> +<code>eclipse-SDK-4.6-linux-gtk-x86_64.tar.gz (64-bit)</code> </p> +<p> To run Eclipse with an alternate Java runtime environment, the path to the Java virtual machine's binary must be identified. With an Eclipse installation from the distribution, altering the $PATH variable to include the path to the alternate Java runtime environment is often not enough as the Eclipse that Linux distributions package often performs a scan internally to pick up GCJ by itself whilst ignoring -what's on the $PATH. An example of the terminal's output is shown below:</p> -<code> searching for compatible vm...<br> -testing /usr/lib/jvm/java-gcj...found </code> -<p>Once the path to the virtual machine's binary has been identified, -try running Eclipse with the following command:</p> -<code>./eclipse -vm /path/to/jre/bin/java</code> -<p>For an actual example, it might look something like the following:</p> -<code> ./eclipse -vm /usr/lib/jvm/sun-java-6/bin/java<br> -./eclipse -vm /opt/sun-jdk-1.6.0.02/bin/java </code> -<p>If this seems to solve the problem, it is likely that the problem +what's on the $PATH. An example of the terminal's output is shown below:<br /> +<code> searching for compatible vm...<br /> +testing /usr/lib/jvm/java-gcj...found </code> </p> +<p> Once the path to the virtual machine's binary has been identified, +try running Eclipse with the following command:<br /> +<code>./eclipse -vm /path/to/jre/bin/java</code> </p> +<p> For an actual example, it might look something like the following:<br /> +<code> ./eclipse -vm /usr/lib/jvm/sun-java-6/bin/java<br /> +./eclipse -vm /opt/sun-jdk-1.6.0.02/bin/java </code> </p> +<p> If this seems to solve the problem, it is likely that the problem really was related to the use of GCJ as the Java runtime for running Eclipse. The eclipse.ini file located within Eclipse's folder can be altered to automatically pass this argument to Eclipse at startup. An -example of its content is presented below:</p> -<code> -showsplash<br> -org.eclipse.platform<br> --vm<br> -/opt/sun-jdk-1.6.0.02/bin/java<br> --vmargs<br> --Xms40m<br> --Xmx512m </code> +example of its content is presented below:<br /> +<code> -showsplash<br /> +org.eclipse.platform<br /> +-vm<br /> +/opt/sun-jdk-1.6.0.02/bin/java<br /> +-vmargs<br /> +-Xms40m<br /> +-Xmx512m </code> </p> <p> Note that every argument must be on its own line. More information about the eclipse.ini file can be found at <a href="http://wiki.eclipse.org/Eclipse.ini">http://wiki.eclipse.org/Eclipse.ini</a>. @@ -544,12 +531,12 @@ you can seek further assistance through the <a href="https://www.eclipse.org/forums/">forums</a>, the IRC <a href="irc://irc.freenode.net/#eclipse">channel</a>, and/or <a href="https://bugs.eclipse.org/bugs/">bugzilla</a>. </p> -<h4><a class="mozTocH4" name="mozTocId3915"></a>Problems with +<h4><a class="mozTocH4" name="mozTocId584602" />Problems with classloaders in created threads</h4> <p> There is a known issue with trying to load classes from a newly-created thread using a class loader different from the plug-in -class loader. The result will be a <code>ClassNotFoundException</code>. As -a workaround, do the following: </p> +class loader. The result will be a <code>ClassNotFoundException</code> +. As a workaround, do the following: </p> <ol> <li>Create a thread in which to run your code.</li> <li>Send yourThread.setContextClassLoader(yourClassLoader); // you @@ -561,17 +548,16 @@ can find your classloader by grabbing a class it loaded competing with other users of the thread (all of Eclipse), so the results will be unpredictable. However, there should be no problem in practice provided you reset the context class loader back to its -original value when your use in the current thread is complete. -(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=8907">8907</a>) -</p> -<h4><a class="mozTocH4" name="mozTocId590607"></a>Deadlock creating +original value when your use in the current thread is complete. (bug <a + href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=8907">8907</a>) </p> +<h4><a class="mozTocH4" name="mozTocId403443" />Deadlock creating executable extension in Plugin.startup</h4> <p> If <code>Plugin.startup</code> code is too complex and performs tasks such as creating an executable extension, a deadlock situation can be created. Only simple bookkeeping tasks should be performed in <code>Plugin.startup</code> code. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=5875">5875</a>) </p> -<h4><a class="mozTocH4" name="mozTocId148431"></a>Potential Problems +<h4><a class="mozTocH4" name="mozTocId984286" />Potential Problems Converting Plug-in Manifests</h4> <p> If your plug-in ships with a plug-in manifest and not an OSGi bundle manifest, is shipped as a JAR file, and contains a nested JAR @@ -581,13 +567,13 @@ exported correctly in the <code>Export-packages</code> bundle manifest header. To work around this you should ship your plug-in with a bundle manifest. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=97689">97689</a>) </p> -<h4><a class="mozTocH4" name="mozTocId544740"></a>Location for Debug +<h4><a class="mozTocH4" name="mozTocId993987" />Location for Debug Options File on Mac OS</h4> <p> If you are running in debug mode on Mac OS, the default location for the .options file is inside the application bundle in the Eclipse.app/Contents/MacOS directory (like the eclipse.ini). (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=88782">88782</a>) </p> -<h4><a class="mozTocH4" name="mozTocId341887"></a>Issues with JNI that +<h4><a class="mozTocH4" name="mozTocId808188" />Issues with JNI that use FindClass</h4> <p> There may be issues when using a JNI implementation that uses FindClass in a function where the JNIEnv pointer is not available, such @@ -607,12 +593,12 @@ use AttachCurrentThread to get the JNIEnv pointer. In this case the application classloader is used.</p> <p>For example, the following will fail because AttachCurrentThread is used to get the JNIEnv pointer:</p> -<pre>static JavaVM* jvm; // Global variable<br><br>void myCallback(void) {<br> JNIEnv* env;<br> jvm->AttachCurrentThread((void**)&env, NULL);<br> // Fails if some/class is not in the application classloader:<br> jclass cls = env->FindClass("some/class");<br> jmethodID methodID = env->GetMethodID(cls, "methodName",<br> "(Ljava/lang/String;)V or whatever signature");<br> env->CallVoidMethod(callback, methodID, ...);<br> jvm->DetachCurrentThread();<br> }<br>}<br></pre> +<pre>static JavaVM* jvm; // Global variable<br /><br />void myCallback(void) {<br /> JNIEnv* env;<br /> jvm->AttachCurrentThread((void**)&env, NULL);<br /> // Fails if some/class is not in the application classloader:<br /> jclass cls = env->FindClass("some/class");<br /> jmethodID methodID = env->GetMethodID(cls, "methodName",<br /> "(Ljava/lang/String;)V or whatever signature");<br /> env->CallVoidMethod(callback, methodID, ...);<br /> jvm->DetachCurrentThread();<br /> }<br />}</pre> <p>A solution is to cache the method ID, for example:</p> -<pre>static jmethodID mid; // Global variable<br><br>JNIEXPORT jint JNICALL JNI_OnLoad(JavaVM *vm, void *reserved) {<br>...<br> // Store the JavaVM pointer<br> jvm = vm;<br><br> // Find the class and store the method ID<br> // Will use the class loader that loaded the JNI library<br> jclass cls = env->FindClass(className"some/class");<br> if(!cls) goto ERR;<br><br> mid = env->GetMethodID(cls, "methodName",<br> "(Ljava/lang/String;)V or whatever signature");<br> if(!mid) goto ERR;<br>...<br>}<br><br>void myCallback(void) {<br> JNIEnv* env;<br> jvm->AttachCurrentThread((void**)&env, NULL);<br> env->CallVoidMethod(callback, mid, ...);<br> // Handle error ...<br> jvm->DetachCurrentThread();<br> }<br>}<br></pre> -<h3 id="I-Platform-Ant"><a class="mozTocH3" name="mozTocId961605"></a>Platform +<pre>static jmethodID mid; // Global variable<br /><br />JNIEXPORT jint JNICALL JNI_OnLoad(JavaVM *vm, void *reserved) {<br />...<br /> // Store the JavaVM pointer<br /> jvm = vm;<br /><br /> // Find the class and store the method ID<br /> // Will use the class loader that loaded the JNI library<br /> jclass cls = env->FindClass(className"some/class");<br /> if(!cls) goto ERR;<br /><br /> mid = env->GetMethodID(cls, "methodName",<br /> "(Ljava/lang/String;)V or whatever signature");<br /> if(!mid) goto ERR;<br />...<br />}<br /><br />void myCallback(void) {<br /> JNIEnv* env;<br /> jvm->AttachCurrentThread((void**)&env, NULL);<br /> env->CallVoidMethod(callback, mid, ...);<br /> // Handle error ...<br /> jvm->DetachCurrentThread();<br /> }<br />}</pre> +<h3 id="I-Platform-Ant"><a class="mozTocH3" name="mozTocId324774" />Platform - Ant</h3> -<h4><a class="mozTocH4" name="mozTocId442280"></a>Custom Ant tasks and +<h4><a class="mozTocH4" name="mozTocId480194" />Custom Ant tasks and Ant types must be separate from plug-in library JARs</h4> <p> Including the class files for custom Ant tasks or Ant types in the regular code JAR for your plug-in causes problems. These class files @@ -623,7 +609,7 @@ types are loaded by the 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> -<h4><a class="mozTocH4" name="mozTocId755617"></a>XDoclet support from +<h4><a class="mozTocH4" name="mozTocId912215" />XDoclet support from within Eclipse</h4> <p> Since there are differences when running Ant from the commandline and within Eclipse, some extra steps may be needed to have XDoclet @@ -631,7 +617,7 @@ support function correctly within Eclipse. Problems may occur creating XDoclet subtasks. The workarounds and full discussion can be found in bug report. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37070">37070</a>) </p> -<h4><a class="mozTocH4" name="mozTocId954641"></a>Ant Editor code +<h4><a class="mozTocH4" name="mozTocId31051" />Ant Editor code completion based on Ant 1.6.x</h4> <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. @@ -639,11 +625,11 @@ Code completion proposals are mostly based on Ant 1.6.x with some updates to Ant 1.8.3 (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=193046">bug 193046</a>) </p> -<h4><a class="mozTocH4" name="mozTocId260211"></a>Setting build loggers +<h4><a class="mozTocH4" name="mozTocId925603" />Setting build loggers not supported when debugging Ant builds</h4> <p> When debugging Ant builds within Eclipse, setting <code>-logger</code> as a program argument will be ignored. </p> -<h4><a class="mozTocH4" name="mozTocId642196"></a>Renaming an External +<h4><a class="mozTocH4" name="mozTocId669417" />Renaming an External Tool builder set to run during auto-build will cause errors</h4> <p> If you rename an existing external tool builder that is configured to run during auto-builds, you will get the following error: Errors @@ -653,14 +639,14 @@ not be found. The workaround is to first disable the builder for auto-builds and then rename the builder. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=118294">118294</a>) </p> -<h4><a class="mozTocH4" name="mozTocId375822"></a>Slow typing/saving of +<h4><a class="mozTocH4" name="mozTocId772119" />Slow typing/saving of the Ant editor with imports that define numerous macrodefs</h4> <p> The Ant editor is slow on saving with buildfiles that have <import> declarations of buildfiles that have numerous <macrodef>s. See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=125117">125117</a> for a possible workaround </p> -<h4><a class="mozTocH4" name="mozTocId525690"></a>Ant 1.8.x reports +<h4><a class="mozTocH4" name="mozTocId715004" />Ant 1.8.x reports missing libraries as build failures</h4> <p> 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 @@ -676,8 +662,8 @@ please refer to the <a href="http://ant.apache.org/manual/install.html#optionalTasks">Optional Tasks</a> section in the Ant manual. </p> <h3 id="I-Platform-User-Assistance"><a class="mozTocH3" - name="mozTocId1352"></a>Platform - User Assistance</h3> -<h4><a class="mozTocH4" name="mozTocId983547"></a>Welcome page not + name="mozTocId876322" />Platform - User Assistance</h3> +<h4><a class="mozTocH4" name="mozTocId828477" />Welcome page not displayed properly (Linux/Unix)</h4> <p> The default Welcome implementation is HTML-based and requires a supported browser in order to work. If no supported browser can be @@ -686,21 +672,21 @@ a different (simpler) appearance. Consult the <a href="http://www.eclipse.org/swt/faq.php#browserplatforms">SWT FAQ</a> for supported browsers and setting up your browser to work with eclipse. </p> -<h4><a class="mozTocH4" name="mozTocId549237"></a>Help browser tool bar +<h4><a class="mozTocH4" name="mozTocId26110" />Help browser tool bar buttons do not work for some documents</h4> <p> The Help browser's Print, Synchronize, and Bookmark buttons do not work for pages that are not actually installed with the product. However, you can always use the print command in the browser's context menu to print the page you're reading. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=44216">44216</a>) </p> -<h4><a class="mozTocH4" name="mozTocId705626"></a>Help documents not +<h4><a class="mozTocH4" name="mozTocId324012" />Help documents not displayed in a browser or very slow document loading (Windows only)</h4> -If your LAN settings are not properly configured for local host access, -your Help browser might open to a blank page or display an HTTP error -instead of a help page, or you may experience long delays when loading -help documents. Your system administrator can configure your LAN -settings so that help documents can be accessed from the local help -server. +<p>If your LAN settings are not properly configured for local host +access, your Help browser might open to a blank page or display an HTTP +error instead of a help page, or you may experience long delays when +loading help documents. Your system administrator can configure your +LAN settings so that help documents can be accessed from the local help +server.</p> <blockquote> <ol> <li>In the Control Panel, open <b>Internet Options</b>, select the @@ -716,31 +702,32 @@ settings, and are not sure that the script is correct, clear the "Use automatic configuration script" check box.</li> </ol> </blockquote> -<h4><a class="mozTocH4" name="mozTocId139783"></a>Working disconnected +<h4><a class="mozTocH4" name="mozTocId227368" />Working disconnected from the network (Windows only)</h4> -If you are experiencing problems when not connected to the network, you -must install the loopback adapter from the Windows installation CD. +<p> If you are experiencing problems when not connected to the network, +you must install the loopback adapter from the Windows installation CD. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=831">831</a>) -<h4><a class="mozTocH4" name="mozTocId519549"></a>Using Internet -Explorer in offline mode (Windows only)</h4> -If you have been using Internet Explorer in Offline mode, when you +</p> +<h4><a class="mozTocH4" name="mozTocId121403" />Using Internet Explorer +in offline mode (Windows only)</h4> +<p>If you have been using Internet Explorer in Offline mode, when you access the help system you will get a message indicating that the web page you requested is not available offline or a blank page will display. Click <b>Connect</b> or deselect "Work Offline" in the -Internet Explorer "File" menu to return the system behavior to normal. -<h3 id="I-Platform-UI"><a class="mozTocH3" name="mozTocId516525"></a>Platform +Internet Explorer "File" menu to return the system behavior to normal.</p> +<h3 id="I-Platform-UI"><a class="mozTocH3" name="mozTocId683637" />Platform - UI</h3> -<h4><a class="mozTocH4" name="mozTocId828423"></a>Dirty state not -tracked properly for OLE documents (Windows only)</h4> +<h4><a class="mozTocH4" name="mozTocId348035" />Dirty state not tracked +properly for OLE documents (Windows only)</h4> <p> The dirty state for an OLE document is not updated properly. This causes Eclipse to prompt to save the contents of the editor when the document is 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> -<h4><a class="mozTocH4" name="mozTocId212451"></a>OLE document crashes +<h4><a class="mozTocH4" name="mozTocId878052" />OLE document crashes can cause Eclipse to also crash (Windows only)</h4> <p>If an OLE document crashes, Eclipse can crash, or the workbench menus can become inconsistent.</p> -<h4><a class="mozTocH4" name="mozTocId190553"></a>Toolbars only +<h4><a class="mozTocH4" name="mozTocId452707" />Toolbars only containing contributed controls exhibit display errors on Mac/Linux</h4> <p> Currently there is no way on the Max or Linux platforms to define the <b>height</b> for controls contributed to toolbars, nor will those @@ -749,50 +736,25 @@ method. If you encounter this issue there is currently no truly viable workaround. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=183003">183003</a>) </p> -Allocating enough memory and solving OutOfMemoryError +<h4><a class="mozTocH4" name="mozTocId443682" />Allocating enough +memory and solving OutOfMemoryError</h4> <p> The native launcher checks the JVM but PDE launches simply use java and don't go through the native launchers. The workaround is to add the appropriate JVM arg to your launch config or to the <i>Preferences > Java > Installed JREs</i>. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=339763">339763</a>) </p> -<h4><a class="mozTocH4" name="mozTocId434307"></a>Capabilities and +<h4><a class="mozTocH4" name="mozTocId862142" />Capabilities and Activities don't affect the menus and toolbars</h4> <p> Capabilities used to hide GUI elements like menu entries work for commands and individual actionSet entries, but Capabilities have not been fully implemented. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=359778">359778</a>) </p> -<h3 id="I-Platform-SWT"><a class="mozTocH3" name="mozTocId694051"></a>Platform +<h3 id="I-Platform-SWT"><a class="mozTocH3" name="mozTocId554478" />Platform - SWT</h3> -<h4><a class="mozTocH4" name="mozTocId191730"></a>SWT Browser widget -crashes when run with XULRunner 31 run-time (Linux only)</h4> -<p> Creation of an SWT Mozilla style Browser with XULRunner 31 run-time -crashes on Linux. The workaround is to use other supported XULRunner -run-times or webkit which is the default on Linux. (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=467646">467646</a>) -</p> -<h4><a class="mozTocH4" name="mozTocId381643"></a>Download progress -window not shown with XULRunner 31 run-time</h4> -<p> Trying to download a file in a SWT Mozilla style Browser using -XULRunner 31 run-time doesn't work and the download progress window -doesn't open automatically. Workaround is to open the download -progress-bar dialog by opening -chrome://mozapps/content/downloads/downloads.xul and manually re-start -the download action. (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=467203">467203</a>) -</p> -<h4><a class="mozTocH4" name="mozTocId568065"></a>Eclipse crashes -randomly when using the Webkit based browser on RHEL 6.5</h4> -<p> The Webkit version (1.2.6) that is bundled with RHEL 6.5 crashes -randomly while evaluating Javascript code. This has been fixed in more -recent versions of Webkit which are not available on RHEL 6.5 yet. The -workaround is to force Eclipse to use the Mozilla XULRunner based -browser. (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=428347">428347</a>) -</p> -<h4><a class="mozTocH4" name="mozTocId353468"></a>Eclipse plug-in based -on the SWT Browser throws exception</h4> +<h4><a class="mozTocH4" name="mozTocId69222" />Eclipse plug-in based on +the SWT Browser throws exception</h4> <p> The SWT Browser widget uses a platform-specific web browser to render HTML. The org.eclipse.swt.SWTError exception ("No more handles") is thrown on platforms that don't meet the requirements for running the @@ -800,112 +762,38 @@ Browser widget. Supported platforms and prerequisites are listed on the SWT FAQ item <a href="http://www.eclipse.org/swt/faq.php#browserplatforms"> "Which platforms support the SWT Browser?"</a>. </p> -<h4><a class="mozTocH4" name="mozTocId664550"></a>Table background is -not painted correctly when SWT.EraseItem is used (specific versions of -GTK3)</h4> -<p> With GTK3 versions > 3.9 and <= 3.14.8, the Table background -is not painted correctly when SWT.EraseItem listener is used. (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=468208">468208</a>) -</p> -<h4><a class="mozTocH4" name="mozTocId998858"></a>TreeItems with -decorated icons overwrite text with Eclipse dark theme on GTK+ 3.10 and -above</h4> -<p> When using the Eclipse dark theme on GTK+ 3.10 and above, TreeItem -widgets with decorated icons (for example, Package Explorer with icons -decorated by EGit to indicate changed files) have their text and/or -background drawn outside the Tree area, possibly overdrawing on other -widgets. (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=465911">465911</a>) -</p> -<h4><a class="mozTocH4" name="mozTocId618828"></a>Some -keybindings/shortcuts become unresponsive (GTK3 only)</h4> -<p> While using GTK+ 3 on Linux (the default in 4.6 release), it is -possible that the keyboard shortcuts stop working all of a sudden. This -is because of a known problem with GTK3/Xinput2 and can be worked -around by setting the environment variable <code>"GDK_CORE_DEVICE_EVENTS=1"</code> -before running the application. Note that this workaround is not -necessary for Eclipse (as the launcher already sets it) but is needed -for other SWT based applications. (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=435742">435742</a>) +<h4><a class="mozTocH4" name="mozTocId519796" />SWT Browser widget +crashes when run with XULRunner 31 run-time (Linux only)</h4> +<p> Creation of an SWT Mozilla style Browser with XULRunner 31 run-time +crashes on Linux. The workaround is to use other supported XULRunner +run-times or webkit which is the default on Linux. (bug <a + href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=467646">467646</a>) </p> -<h4><a class="mozTocH4" name="mozTocId403331"></a>Eclipse crashes with -GTK+ 2 and Oxygen-gtk2 theme under KDE desktop</h4> -<p> Eclipse crashes when running on KDE using GTK+ 2 and the -corresponding desktop theme "Oxygen-gtk2" with a message similar to:<br> -<code>"java: -/build/buildd/gtk2-engines-oxygen-1.4.5/src/animations/oxygencomboboxdata.cpp:87: -void Oxygen::ComboBoxData::setButton(GtkWidget*): Assertion -`!_button._widget' failed."</code> <br> -For details, see bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=440660">440660</a>. -The possible workarounds are: </p> -<ol> - <li>Use Eclipse with GTK+ 3 (the default in 4.6 release) and the -corresponding theme "Oxygen-gtk3".</li> - <li>Use a newer version of the "Oxygen-gtk2" theme in which the above -bug has been fixed.</li> - <li>In case versions of GTK+ and/or the theme cannot be altered, edit -the existing file "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc" and -change<br> - <code>GtkComboBox::appears-as-list = 1</code> into <code>GtkComboBox::appears-as-list -= 0.</code> </li> -</ol> -<h4><a class="mozTocH4" name="mozTocId437801"></a>Eclipse hangs when -pasting from an unresponsive application (GTK only)</h4> -<p> If the application that is supplying the clipboard material is -unresponsive, the paste operation hangs Eclipse for several minutes. -This situation can be encountered when copying from an Eclipse target -workbench, suspending the target 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> -<h4><a class="mozTocH4" name="mozTocId556263"></a>IME conversion -problem (Solaris GTK only)</h4> +<h4><a class="mozTocH4" name="mozTocId664509" />IME conversion problem +(Solaris GTK only)</h4> <p> When typing Japanese text, the conversion to Kanji must be done one ideogram at a time. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=226636">226636</a>) </p> -<h4><a class="mozTocH4" name="mozTocId944641"></a>Eclipse won't start +<h4><a class="mozTocH4" name="mozTocId516202" />Eclipse won't start (Linux GTK PPC only)</h4> <p> Eclipse fails to create a lock file with reason "No locks available". To launch eclipse you must disable file locking using the osgi.locking property. For example, you could launch eclipse as -follows: <br> +follows: <br /> <code>eclipse -vmargs -Dosgi.locking=none</code> </p> -<h4><a class="mozTocH4" name="mozTocId900336"></a>Older versions of -some Windows screen readers no longer work with Eclipse</h4> -<p>JAWS versions 8 and 9 and Window-Eyes version 6 no longer work well -with Eclipse and other SWT applications. Window-Eyes 6 will cause -Eclipse to crash, and JAWS 8 and 9 can cause SWT applications to crash. -This happens because IAccessible2 support was added to SWT for Eclipse -3.7, but these older screen reader versions contain partial -implementations of IAccessible2 that do not follow the current -IAccessible2 specification.</p> -<p> The workaround for these cases is to specify Java property <code>org.eclipse.swt.accessibility.UseIA2</code> -with value <code>false</code> , which will instruct SWT to not attempt -to use IA2 interfaces. An easy way to set this property is to specify -VM argument <code>-Dorg.eclipse.swt.accessibility.UseIA2=false</code> -when launching Eclipse or your SWT application. (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=313182">313182</a>) -</p> -<h4><a class="mozTocH4" name="mozTocId436984"></a>Menu on TaskItem -doesn't work for an SWT application when AppName is not set on Windows</h4> -<p> When AppName is not set for an SWT application, specify AppName -using <code>Display.setAppName()</code> to be able to set Menu to the -TaskItem. (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=445840">445840</a>) -</p> -<h4><a class="mozTocH4" name="mozTocId759240"></a>Eclipse icon is +<h4><a class="mozTocH4" name="mozTocId238090" />Eclipse icon is duplicated in task-bar on Windows</h4> <p> Workaround is to pin the launched eclipse application and not the launcher, for more details, refer bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=314805">314805</a> </p> -<h4><a class="mozTocH4" name="mozTocId220079"></a>BIDI Segments in Text +<h4><a class="mozTocH4" name="mozTocId414883" />BIDI Segments in Text controls</h4> <p> BIDI Segments in Text controls only work on Windows and GTK. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=388578">388578</a>) </p> -<h4><a class="mozTocH4" name="mozTocId638859"></a>Block Selection +<h4><a class="mozTocH4" name="mozTocId518357" />Block Selection functionality provided by StyledText is not BIDI aware</h4> <p> When the orientation of characters under the left and right edges of the block selection rectangle are not the same, the actual selection @@ -913,14 +801,13 @@ ranges (in memory) differ from the visual representation of the selection. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=277929">277929</a>) </p> -<h3 id="I-Platform-Team-CVS"><a class="mozTocH3" name="mozTocId812923"></a>Platform +<h3 id="I-Platform-Team-CVS"><a class="mozTocH3" name="mozTocId263012" />Platform - Team - CVS</h3> <p> The following are known problems with the CVS repository provider only, and do not apply to other repository providers. Additional information on how to use CVS from Eclipse can be found in the <a href="https://wiki.eclipse.org/CVS_FAQ">Eclipse CVS FAQ</a>. </p> -<h4><a class="mozTocH4" name="mozTocId593797"></a>CVS server -compatibility</h4> +<h4><a class="mozTocH4" name="mozTocId262771" />CVS server compatibility</h4> <p>The CVS plug-in parses messages returned from the CVS server. If the format of these messages is not as expected, some of the plug-in's functionality may be missing. The CVS plug-in is compatible with all @@ -932,14 +819,14 @@ However, future releases could easily break the Eclipse CVS client. Basic functionality, such as Checkout, Commit, and Update, should always work, but there may be problems with more advanced commands such as Synchronizing and Browsing the repository.</p> -<h4><a class="mozTocH4" name="mozTocId640505"></a>Connection cannot be +<h4><a class="mozTocH4" name="mozTocId532855" />Connection cannot be found after initially missing</h4> <p> If a connection initially fails due to a network problem, the connection may continue to fail even when the network problem is fixed. In order to establish the connection you must exit and restart Eclipse. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=9295">9295</a>) </p> -<h4><a class="mozTocH4" name="mozTocId200631"></a>"Received broken pipe +<h4><a class="mozTocH4" name="mozTocId660590" />Received broken pipe signal" error from server</h4> <p> Eclipse sometimes performs multiple commands within a single connection to the server. This may cause problems with CVS servers that @@ -947,14 +834,14 @@ are running server scripts in response to certain commands. (bugs <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=23575">23575</a> and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=23581">23581</a>) </p> -<h4><a class="mozTocH4" name="mozTocId500486"></a>"Terminated with -fatal signal 10" error from server</h4> +<h4><a class="mozTocH4" name="mozTocId971246" />Terminated with fatal +signal 10" error from server</h4> <p> There is a bug in the CVS server related to some compression levels. If you get this error, changing the compression level on the CVS preference page may help. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=15724">15724</a>) </p> -<h4><a class="mozTocH4" name="mozTocId987364"></a>"Unknown response" -error using ext connection method</h4> +<h4><a class="mozTocH4" name="mozTocId689776" />error using ext +connection method</h4> <p> There are a few situations that can result in an "Unknown response" error messages when using the ext connection method. One situation involves using an external communications client (e.g. rsh or ssh) that @@ -963,7 +850,7 @@ adds CRs to the communications channel (bug <a Another involves Eclipse not properly reading the stderr output of the external communications tool. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=11633">11633</a>) </p> -<h4><a class="mozTocH4" name="mozTocId122538"></a>A disabled CVS +<h4><a class="mozTocH4" name="mozTocId50418" />A disabled CVS capability may not be auto-enabled in existing workspaces</h4> <p> New in 3.0 is the ability to disable capabilities and the CVS support in Eclipse can be disabled. However, for backwards @@ -971,11 +858,11 @@ compatibility the CVS capability is auto-enabled in existing workspaces that already contain CVS projects. The auto-enabling function may not run if the team support plugin is not loaded at startup. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66977">66977</a>) </p> -<h4><a class="mozTocH4" name="mozTocId881444"></a>Builder output files +<h4><a class="mozTocH4" name="mozTocId533799" />Builder output files may appear as changed</h4> <p>When folders containing build output are shared they may get improperly marked as dirty when build output is generated.</p> -<h4><a class="mozTocH4" name="mozTocId83566"></a>Enabling GNOME proxy +<h4><a class="mozTocH4" name="mozTocId253283" />Enabling GNOME proxy support</h4> <p> GNOME applications can make use of proxy settings defined in this environment. If set, Eclipse will use it prior to proxy settings @@ -984,22 +871,22 @@ enable it launch Eclipse with <code>"-Dorg.eclipse.core.net.enableGnome"</code> switch. That is, </p> <pre>eclipse -Dorg.eclipse.core.net.enableGnome</pre> <h3 id="I-Platform-Install-Update"><a class="mozTocH3" - name="mozTocId693443"></a>Platform - Install/Update</h3> -<h4><a class="mozTocH4" name="mozTocId78143"></a>Manually installing + name="mozTocId805874" />Platform - Install/Update</h3> +<h4><a class="mozTocH4" name="mozTocId914600" />Manually installing features and plug-ins on a FAT file system (Windows only)</h4> <p>When features and plug-ins are manually installed on top of an Eclipse-based product install located on a FAT file system that has already been run at least once, the product must be explicitly restarted with -clean. That is,</p> -<pre>eclipse.exe -clean<br></pre> -<h4><a class="mozTocH4" name="mozTocId327444"></a>Connecting to -untrusted sites using https</h4> +<pre>eclipse.exe -clean</pre> +<h4><a class="mozTocH4" name="mozTocId648565" />Connecting to untrusted +sites using https</h4> <p>You cannot install or update software from a site using https whose certificate is not chained to a trusted root certificate in your local certificate store. This typically means the server is using a self-signed certificate, or a certificate authenticated by an unknown third party.</p> -<h4><a class="mozTocH4" name="mozTocId712235"></a>Extension location is +<h4><a class="mozTocH4" name="mozTocId104394" />Extension location is lost if the install path changes</h4> <p> A previously configured extension location may be temporarily removed if the install is moved or mounted under a different path. This @@ -1008,53 +895,52 @@ uses a relative path that points to a directory under the Eclipse install. On a second startup using the same install path, the extension location is added again (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95403">95403</a>). -<br> </p> -<h3 id="I-JDT"><a class="mozTocH3" name="mozTocId170641"></a>Java +<h3 id="I-JDT"><a class="mozTocH3" name="mozTocId428861" />Java development tools (JDT)</h3> -<h4><a class="mozTocH4" name="mozTocId246992"></a>Multiple regions +<h4><a class="mozTocH4" name="mozTocId180305" />Multiple regions formatting in a given source snippet</h4> -In version 3.4, the API method <code>org.eclipse.jdt.core.formatter.CodeFormatter.format(int, +<p>In version 3.4, the API method <code>org.eclipse.jdt.core.formatter.CodeFormatter.format(int, String, IRegion[], int, String)</code> was added to allow the -formatting of several regions in a source snippet with a single pass. <br> +formatting of several regions in a source snippet with a single pass. <br /> Even if specified, this method does not currently accept comments of -the following kinds: +the following kinds:</p> <ul> <li><code>org.eclipse.jdt.core.formatter.CodeFormatter#K_SINGLE_LINE_COMMENT</code></li> <li><code>org.eclipse.jdt.core.formatter.CodeFormatter#K_MULTI_LINE_COMMENT</code></li> <li><code>org.eclipse.jdt.core.formatter.CodeFormatter#K_JAVA_DOC</code></li> </ul> -This will be fixed in a future release (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=233967">233967</a>). -<h4><a class="mozTocH4" name="mozTocId472358"></a>Searching for -constant field references</h4> +<p>This will be fixed in a future release (bug <a + href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=233967">233967</a>).</p> +<h4><a class="mozTocH4" name="mozTocId589358" />Searching for constant +field references</h4> <p> Search does not find references to constant fields inside binaries because the Java Language Specification mandates that constant field values be inlined in the class file's byte codes, leaving no trace of a -field reference. (bug <a +field reference. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=12044">12044</a>) </p> -<h4><a class="mozTocH4" name="mozTocId990768"></a>Cut, copy, paste not +<h4><a class="mozTocH4" name="mozTocId577868" />Cut, copy, paste not working for linked resources in views showing Java elements</h4> <p> The cut, copy, and paste actions do not work for linked files and folders appearing in views that show Java elements, including the Package Explorer. The 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> -<h4><a class="mozTocH4" name="mozTocId876065"></a>Java working sets not +<h4><a class="mozTocH4" name="mozTocId554543" />Java working sets not working correctly for elements from JRE system library container</h4> <p> Applying a working set consisting entirely of elements from the JRE System library container as a filter to the packages view might result in an empty Package Explorer. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=30442">30442</a>) </p> -<h4><a class="mozTocH4" name="mozTocId760232"></a>Breakpoints -unreliable running Sun 1.6.0_14</h4> -Developers debugging applications on Sun's 1.6.0_14 virtual machine +<h4><a class="mozTocH4" name="mozTocId157019" />Breakpoints unreliable +running Sun 1.6.0_14</h4> +<p>Developers debugging applications on Sun's 1.6.0_14 virtual machine should be aware that breakpoints are unreliable (i.e. do not always suspend execution). The problem occurs on Windows and Linux platforms. This is an issue with the VM and not with Eclipse. 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>). -<h4><a class="mozTocH4" name="mozTocId157025"></a>Suspend on uncaught + href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=279137">279137</a>).</p> +<h4><a class="mozTocH4" name="mozTocId440090" />Suspend on uncaught exception overrides exception breakpoint location filters</h4> <p> Exception breakpoints can be configured with location filters (inclusive and exclusive). When an unchecked exception is configured to @@ -1062,14 +948,14 @@ exception overrides exception breakpoint location filters</h4> suspend when the user preference to suspend on uncaught exceptions is on. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66770">66770</a>) </p> -<h4><a class="mozTocH4" name="mozTocId209402"></a>Running Java programs +<h4><a class="mozTocH4" name="mozTocId812347" />Running Java programs with non-Latin-1 characters in package or class names</h4> -You get a <code>java.lang.NoClassDefFoundError</code> when running +<p>You get a <code>java.lang.NoClassDefFoundError</code> when running Java programs with non-Latin characters in the package or class names. The workaround is to package the class files as a JAR file and run the program out of the JAR and not from the file system directly. (bug <a - href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=4181">4181</a>) -<h4><a class="mozTocH4" name="mozTocId573670"></a>Cannot run or debug + href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=4181">4181</a>)</p> +<h4><a class="mozTocH4" name="mozTocId638407" />Cannot run or debug class in a project with GB18030 characters in project name</h4> <p> Most class libraries do not properly support the creation of a system process (via <code>java.lang.Runtime.exec(...)</code> ) when @@ -1077,13 +963,13 @@ the specified command line contains GB18030 characters. This limitation means the debugger cannot launch applications when the command line it generates contains GB18030 characters. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32206">32206</a>) </p> -<h4><a class="mozTocH4" name="mozTocId78501"></a>Cannot detect -installed JRE with GB18030 characters in path name</h4> +<h4><a class="mozTocH4" name="mozTocId994970" />Cannot detect installed +JRE with GB18030 characters in path name</h4> <p> Automatic JRE detection fails when the JRE is stored in a directory containing GB18030 characters in its name. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=33844">33844</a>) </p> -<h4><a class="mozTocH4" name="mozTocId633891"></a>Cannot generate -Javadoc for packages with GB18030 characters in the name</h4> +<h4><a class="mozTocH4" name="mozTocId324283" />Cannot generate Javadoc +for packages with GB18030 characters in the name</h4> <p> Most class libraries do not properly support the creation of a system process (via <code>java.lang.Runtime.exec(...)</code> ) when the specified command line contains GB18030 characters. Since Javadoc @@ -1091,7 +977,7 @@ is created using the Javadoc executable provided with the JDK, generating Javadoc fails if the package or class name contains GB18030 characters. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=32215">32215</a>) </p> -<h4><a class="mozTocH4" name="mozTocId27992"></a>Unable to debug stack +<h4><a class="mozTocH4" name="mozTocId524553" />Unable to debug stack overflows</h4> <p> If a debug session suspends on a <code>java.lang.StackOverflowError</code> exception (due to an exception breakpoint), the debugger may not be @@ -1099,7 +985,7 @@ able to retrieve any debug information from the target JVM. As well, the debugger may 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> -<h4><a class="mozTocH4" name="mozTocId970095"></a>Evaluation limitation</h4> +<h4><a class="mozTocH4" name="mozTocId162517" />Evaluation limitation</h4> <p> The debugger uses threads in the target JVM to perform evaluations (both explicit evaluations that the user requests, and implicit evaluations such as <code>toString()</code> invocations in the <b>Variables</b> @@ -1114,23 +1000,22 @@ thread that is not in a valid state to perform an evaluation, an error message will appear to the effect of "Thread must be suspended by step or breakpoint to perform method invocation". (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34440">34440</a>) </p> -<h4><a class="mozTocH4" name="mozTocId698026"></a>Missing debug -attributes</h4> -The debugger requires that class files be compiled with debug +<h4><a class="mozTocH4" name="mozTocId408387" />Missing debug attributes</h4> +<p>The debugger requires that class files be compiled with debug attributes if it is to be able to display line numbers and local variables. Quite often, class libraries (for example, " <code>rt.jar</code> ") are compiled without complete debug attributes, and thus local variables and method arguments for those classes are not visible in the -debugger. -<h4><a class="mozTocH4" name="mozTocId11693"></a>Using Hot Code Replace</h4> +debugger.</p> +<h4><a class="mozTocH4" name="mozTocId330034" />Using Hot Code Replace</h4> <p>Hot code replace is supported on JDK 1.4.x VMs, and IBM J9 VMs. The debugger will attempt to replace all class files that change in the workspace as the user edits and builds source code. However, hot code replace is limited to changes that a particular virtual machine implementation supports. For example, changes within existing methods may be supported, but the addition or removal of members may not be.</p> -<h4><a class="mozTocH4" name="mozTocId736358"></a>Scrapbook</h4> -Setting a breakpoint inside a scrapbook page is not supported. +<h4><a class="mozTocH4" name="mozTocId976120" />Scrapbook</h4> +<p>Setting a breakpoint inside a scrapbook page is not supported.</p> <p> When a snippet is run in the scrapbook which directly or indirectly calls <code>System.exit(int)</code> , the evaluation cannot be completed, and will result in a stack trace for a <code>com.sun.jdi.VMDisconnectedException</code> @@ -1138,45 +1023,46 @@ being displayed in the scrapbook editor. </p> <p> Terminating a scrapbook page while it is performing an evaluation results in a <code>com.sun.jdi.VMDisconnectedException</code> being displayed in the scrapbook editor. </p> -<h4><a class="mozTocH4" name="mozTocId233701"></a>Debugging over slow +<h4><a class="mozTocH4" name="mozTocId666507" />Debugging over slow connections</h4> -A global Java debug preference specifies the debugger timeout, which is -the maximum amount of time the debugger waits for a response from the -target VM after making a request of that VM. Slow connections may +<p>A global Java debug preference specifies the debugger timeout, which +is the maximum amount of time the debugger waits for a response from +the target VM after making a request of that VM. Slow connections may require that this value be increased. The timeout value can be edited from the <b>Java > Debug </b>preference page. Changing the timeout value only affects subsequently launched VM, not VMs that are already -running. -<h4><a class="mozTocH4" name="mozTocId550867"></a>Updating of inspected +running.</p> +<h4><a class="mozTocH4" name="mozTocId207158" />Updating of inspected values</h4> -When inspecting the result of an evaluated expression in the debugger, -it is important to note that the result displayed is the result of that -expression at the time it was evaluated. For example, when inspecting a -simple integer counter (primitive data type), the value displayed in -the Expressions view is the value when the expression was evaluated. As -the counter is changed in the running program, the inspected result -will not change (since the view is not displaying the value bound to a -variable - it is displaying the value of an expression, and the value -of a primitive data type cannot change). However, if an expression -results in an object, fields of that object will be updated in the -inspector as they change in the running program (since the value bound -to fields in an object can change). -<h4><a class="mozTocH4" name="mozTocId579316"></a>Stepping over native +<p>When inspecting the result of an evaluated expression in the +debugger, it is important to note that the result displayed is the +result of that expression at the time it was evaluated. For example, +when inspecting a simple integer counter (primitive data type), the +value displayed in the Expressions view is the value when the +expression was evaluated. As the counter is changed in the running +program, the inspected result will not change (since the view is not +displaying the value bound to a variable - it is displaying the value +of an expression, and the value of a primitive data type cannot +change). However, if an expression results in an object, fields of that +object will be updated in the inspector as they change in the running +program (since the value bound to fields in an object can change).</p> +<h4><a class="mozTocH4" name="mozTocId821393" />Stepping over native methods that perform I/O</h4> -When the debugger steps over native methods that perform I/O to <code>System.out</code> -or <code>System.err</code> , the output may not appear immediately -unless the native performs a flush on the output buffer. -<h4><a class="mozTocH4" name="mozTocId513966"></a>VM and process +<p>When the debugger steps over native methods that perform I/O to <code>System.out</code> +or <code>System.err</code>, the output may not appear immediately +unless the native performs a flush on the output buffer.</p> +<h4><a class="mozTocH4" name="mozTocId724969" />VM and process termination running on IBM 1.3 JVM on Linux (Linux only)</h4> -Terminating a launch, debug target, or system process associated with a -debug target running on the IBM 1.3 JVM on the Linux platform does not -work when the associated debug target has a suspended thread. To remove -such debug targets from the debug UI, select <b>Terminate and Remove</b> -from the debug view's pop-up menu (or use the shortcut "delete" key). -Associated system processes in the OS may not be properly cleaned up. -If a debug target has no suspended threads, termination works properly. -(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=1631">1631</a>) -<h4><a class="mozTocH4" name="mozTocId726887"></a>Java Annotation +<p>Terminating a launch, debug target, or system process associated +with a debug target running on the IBM 1.3 JVM on the Linux platform +does not work when the associated debug target has a suspended thread. +To remove such debug targets from the debug UI, select <b>Terminate +and Remove</b> from the debug view's pop-up menu (or use the shortcut +"delete" key). Associated system processes in the OS may not be +properly cleaned up. If a debug target has no suspended threads, +termination works properly. (bug <a + href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=1631">1631</a>)</p> +<h4><a class="mozTocH4" name="mozTocId606104" />Java Annotation Processing</h4> <p> Some methods in the processing API are unimplemented when compiling within the IDE, and will throw <code>UnsupportedOperationException</code> @@ -1192,7 +1078,7 @@ Slow annotation processors can cause a slowdown of the editing experience. If this occurs, you may wish to turn off <b>Enable processing in editor</b> on the <b>Java Compiler > Annotation Processing</b> properties page of your Java project. </p> -<h4><a class="mozTocH4" name="mozTocId838822"></a>Java indexing +<h4><a class="mozTocH4" name="mozTocId188069" />Java indexing encounters problems when a folder is used both as a source and a class folder</h4> <p> Java indexing encounters problems when a folder is used both as a @@ -1203,16 +1089,16 @@ strongly advised to use different folders for sources and binary classes. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=309903">309903</a>) </p> -<h3 id="I-PDE"><a class="mozTocH3" name="mozTocId862851"></a>Plug-in +<h3 id="I-PDE"><a class="mozTocH3" name="mozTocId25456" />Plug-in Development Environment (PDE)</h3> -<h4><a class="mozTocH4" name="mozTocId690680"></a>Feature manifest -editor does not preserve all comments</h4> +<h4><a class="mozTocH4" name="mozTocId179699" />Feature manifest editor +does not preserve all comments</h4> <p> When a non-source page of the feature manifest editor is used, PDE will convert changes back into XML by regenerating the file. Although the overall content and 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> -<h4><a class="mozTocH4" name="mozTocId587493"></a>PDE will not unzip +<h4><a class="mozTocH4" name="mozTocId243421" />PDE will not unzip source zips of some plug-ins</h4> <p> In the plug-in import wizard, when you choose to import plug-ins as "projects with source folders", PDE will not unzip the source for the @@ -1230,12 +1116,12 @@ by the JDT compiler and may result in unpredictable build behavior. Therefore, PDE always imports org.eclipse.swt as binary with source attached. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66314">66314</a>) </p> -<h4><a class="mozTocH4" name="mozTocId635267"></a>Emacs key bindings do +<h4><a class="mozTocH4" name="mozTocId722932" />Emacs key bindings do not work in manifest editor fields</h4> <p> Non-default key bindings currently do not work in fields on non-source pages of the PDE manifest editors. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=19482">19482</a>) </p> -<h4><a class="mozTocH4" name="mozTocId216192"></a>Export of plug-in may +<h4><a class="mozTocH4" name="mozTocId828449" />Export of plug-in may silently drop classes</h4> <p> When exporting a plug-in using the plug-in, feature or product wizards, some classes might be dropped from the resulting archive if @@ -1243,21 +1129,21 @@ their fully qualified name is too long. This typical path limitation can be worked around by creating the jar of the problematic plug-in by using the Jar export wizard. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=97150">97150</a>) </p> -<h4><a class="mozTocH4" name="mozTocId870661"></a>Compilation errors -when exporting projects not stored outside of the workspace</h4> +<h4><a class="mozTocH4" name="mozTocId89714" />Compilation errors when +exporting projects not stored outside of the workspace</h4> <p> When exporting multiple plug-ins and one is stored outside of the workspace, compile errors occurs on export. To work around the problem, you can either export the plug-ins one by one, or change their location. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=98579">98579</a>) </p> -<h4><a class="mozTocH4" name="mozTocId631939"></a>Headless build needs -to be run from a fully qualified path</h4> +<h4><a class="mozTocH4" name="mozTocId270371" />Headless build needs to +be run from a fully qualified path</h4> <p> When running a headless build using the scripts provided by pde build, the properties <code>builder</code> and <code>buildDirectory</code> must refer to a fully qualified path. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139554">139554</a>) </p> -<h4><a class="mozTocH4" name="mozTocId965166"></a>Importing in Eclipse +<h4><a class="mozTocH4" name="mozTocId73293" />Importing in Eclipse application fails if plug-in exists in host workspace</h4> <p> When running an Eclipse application (self-hosting) importing plug-ins will not work correctly if the plug-in being imported exists @@ -1266,7 +1152,7 @@ target platform of the application to point at the running plug-ins from the host (target weaving). This also affects the PDE test suite. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=294005">294005</a>) </p> -<h4><a class="mozTocH4" name="mozTocId723029"></a>Reusing a workspace +<h4><a class="mozTocH4" name="mozTocId914239" />Reusing a workspace after changing architectures silently breaks PDE models</h4> <p> If a workspace is reused on a machine with a different architecture, the PDE models used to build plug-ins may silently fail. @@ -1274,8 +1160,8 @@ To work around this problem, delete the metadata in <workspace>/.metadata/.plugins/org.eclipse.pde.core. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=350172">350172</a>) </p> -<h4><a class="mozTocH4" name="mozTocId923139"></a>Missing @since tag -API Tools problems on interface fields containing @noreference tag</h4> +<h4><a class="mozTocH4" name="mozTocId624312" />Missing @since tag API +Tools problems on interface fields containing @noreference tag</h4> <p> The Eclipse platform 4.6 release will not allow the API Tools @noreference tag on interface fields. This was changed because all interface fields are constant fields that cannot support the @@ -1286,7 +1172,7 @@ It is recommended that you create an API Tools filter for the missing baseline has been regenerated. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=402393">402393</a>) </p> -<h2 id="RunningEclipse"><a class="mozTocH2" name="mozTocId420991"></a>Running +<h2 id="RunningEclipse"><a class="mozTocH2" name="mozTocId19817" />Running Eclipse</h2> <p> After installing the Eclipse SDK in a directory, you can start the Workbench by running the Eclipse executable included with the release @@ -1297,8 +1183,8 @@ If installed at <code>c:\eclipse-SDK-4.6-win32</code> , the executable is <code>c:\eclipse-SDK-4.6-win32\eclipse\eclipse.exe</code> . <b>Note:</b> Set-up on most other operating environments is analogous. Special instructions for Mac OS X are listed <a href="#macosx">below</a>. </p> -<h3><a class="mozTocH3" name="mozTocId230700"></a>Allocating enough -memory and solving OutOfMemoryErrors</h3> +<h3><a class="mozTocH3" name="mozTocId60052" />Allocating enough memory +and solving OutOfMemoryErrors</h3> <p> By default, Eclipse will allocate up to 1024 megabytes of Java heap memory. This should be ample for all typical development tasks. However, depending on the JRE that you are running, the number of @@ -1317,7 +1203,7 @@ than "1024M" (1024 megabytes -- the default). </p> of available physical memory on your machine will cause Java to "thrash" as it copies objects back and forth to virtual memory, which will severely degrade your performance.</p> -<h3><a class="mozTocH3" name="mozTocId196879"></a>Selecting a workspace</h3> +<h3><a class="mozTocH3" name="mozTocId735187" />Selecting a workspace</h3> <p> When the Workbench is launched, the first thing you see is a dialog that allows you to select where the workspace will be located. The workspace is the directory where your work will be stored. If you do @@ -1327,9 +1213,9 @@ for your projects as well as for holding any required metadata. For shared or multi-workspace installs you must explicitly specify the location for your workspace using the dialog (or via the " <code>-data</code> " command line argument). </p> -<h3><a class="mozTocH3" name="mozTocId266563"></a>Specifying the Java +<h3><a class="mozTocH3" name="mozTocId620725" />Specifying the Java virtual machine</h3> -<p>Here is a typical Eclipse command line: </p> +<p>Here is a typical Eclipse command line:</p> <blockquote> <p> <code>eclipse -vm c:\jdk6u22\jre\bin\javaw</code> </p> </blockquote> @@ -1348,7 +1234,7 @@ append the command line arguments.</li> </ol> <p>Opening this shortcut launches Eclipse. (You can drag the shortcut to the Windows Desktop if you want to keep it in easy reach.)</p> -<h3 id="macosx"><a class="mozTocH3" name="mozTocId228378"></a>Mac OS X</h3> +<h3 id="macosx"><a class="mozTocH3" name="mozTocId928700" />Mac OS X</h3> <p> On Mac OS X, you start Eclipse by double clicking the Eclipse application. If you need to pass arguments to Eclipse, you'll have to edit the <code>eclipse.ini</code> file inside the Eclipse application @@ -1375,7 +1261,7 @@ with significant numbers of resources if you allow Spotlight to index your workspace. To prevent this, start System Preferences, select the Spotlight icon, then the Privacy tab, then click the Add button ("+") and find your workspace directory in the dialog that appears.</p> -<h3 id="SharedInstall"><a class="mozTocH3" name="mozTocId788467"></a>Shared +<h3 id="SharedInstall"><a class="mozTocH3" name="mozTocId221199" />Shared Install</h3> <p> The startup speed of a shared install can be improved if proper cache information is stored in the shared install area. To achieve @@ -1384,10 +1270,10 @@ this, after unzipping Eclipse distribution, run Eclipse once with the install directory. See <a href="%20http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fmulti_user_installs.html">shared installs</a> in Eclipse Help for more information. </p> -<h3 id="SpecialOSRequirements"><a class="mozTocH3" name="mozTocId105865"></a>Special +<h3 id="SpecialOSRequirements"><a class="mozTocH3" name="mozTocId317919" />Special Operating System Requirements</h3> <h4 id="SpecialOSRequirementsAIX"><a class="mozTocH4" - name="mozTocId576803"></a>AIX</h4> + name="mozTocId914102" />AIX</h4> <p>In order for this version of Eclipse to run, GTK2 libraries and their dependencies must be installed and available on the library path (i.e. LIBPATH). These libraries are available from @@ -1400,7 +1286,7 @@ download from the same site.</p> versions 5 and 6. The IBM Developer Kit for AIX can be downloaded from: https://www.ibm.com/developerworks/java/jdk/aix/service.html</p> <h4 id="SpecialOSRequirementsHPUX"><a class="mozTocH4" - name="mozTocId83227"></a>HPUX</h4> + name="mozTocId383156" />HPUX</h4> <p>In order for this version of Eclipse to run, GTK2 libraries must be installed and available on the library path (i.e. LD_LIBRARY_PATH).</p> <p>For example, export LD_LIBRARY_PATH=/opt/gtk_64bit/lib/hpux64/</p> @@ -1412,14 +1298,14 @@ should be used to launch Eclipse:</p> <p>Note you might also need to add the -d64 option to the vmargs when using an Oracle JRE. (-vmargs -d64)</p> <h4 id="SpecialOSRequirementsSolaris"><a class="mozTocH4" - name="mozTocId203915"></a>Solaris</h4> + name="mozTocId2011" />Solaris</h4> <p>This version of Eclipse works best with the latest version of GTK+ 2, but the earliest version supported is GTK+ 2.10.</p> <p>The GTK libraries must be available on the library path (i.e. LD_LIBRARY_PATH).</p> -<h2 id="Upgrading"><a class="mozTocH2" name="mozTocId320201"></a>Upgrading +<h2 id="Upgrading"><a class="mozTocH2" name="mozTocId575572" />Upgrading Workspace from a Previous Release</h2> -<h3><a class="mozTocH3" name="mozTocId35396"></a>Users who don't use +<h3><a class="mozTocH3" name="mozTocId401691" />Users who don't use "-data"</h3> <p>If you weren't previously using "-data" to specify your workspace, follow these steps to upgrade:</p> @@ -1441,8 +1327,7 @@ old Eclipse, you should re-install them in the new Eclipse.</li> the workspace chooser dialog at startup (or use "<code>-data</code>" command line argument to pre-select the workspace location). </li> </ol> -<h3><a class="mozTocH3" name="mozTocId19126"></a>Users who do use -"-data"</h3> +<h3><a class="mozTocH3" name="mozTocId197750" />Users who do use "-data"</h3> <p> If you were previously using the " <code>-data</code> " argument to start Eclipse, your upgrade path is much easier: </p> <ol> @@ -1460,7 +1345,7 @@ command line argument to pre-select the workspace location). </li> you've upgraded your workspace, you won't be able to use it again with an older version of Eclipse. If you ever want to go "back in time" to an earlier release, you will need that backup. </p> -<h3><a class="mozTocH3" name="mozTocId209647"></a>Users who use User +<h3><a class="mozTocH3" name="mozTocId839433" />Users who use User Libraries or classpath containers that contain JARs referencing other libraries via Class-Path in the MANIFEST.MF</h3> <p>If you want the referenced JAR files to be included in the @@ -1471,8 +1356,8 @@ to the <code>-vmargs</code> list on start-up, or </li> <li>Manually add the referenced JARs to the User Library or to the project.</li> </ul> -<h3><a class="mozTocH3" name="mozTocId682919"></a>Dropped in bundles -may not resolve after upgrade</h3> +<h3><a class="mozTocH3" name="mozTocId623237" />Dropped in bundles may +not resolve after upgrade</h3> <p> If you have installed bundles by dropping them into the <code>plugins</code> or <code>dropins</code> directory, they might no longer resolve when you upgrade to a new Eclipse Platform version. In each new version of @@ -1483,10 +1368,10 @@ always recommended that you install software via the <code>Help > Install New Software</code> mechanism so you are made aware of any install-time failure to resolve dependencies. </p> <h2 id="InteroperabilityWithPreviousReleases"><a class="mozTocH2" - name="mozTocId500419"></a>Interoperability with Previous Releases</h2> -<h3><a class="mozTocH3" name="mozTocId155846"></a>Interoperability of + name="mozTocId638978" />Interoperability with Previous Releases</h2> +<h3><a class="mozTocH3" name="mozTocId759237" />Interoperability of Release 4.6 with previous releases</h3> -<h4><a class="mozTocH4" name="mozTocId676468"></a>Sharing projects +<h4><a class="mozTocH4" name="mozTocId226004" />Sharing projects between heterogeneous Eclipse 4.6 and 4.5</h4> <p>Special care is required when a project in a team repository is being loaded and operated on by developers using Eclipse-based products @@ -1545,7 +1430,7 @@ Eclipse 3.5 or earlier. If compatibility with 3.5 or earlier workspace is required, users on 3.5 or earlier workspaces will need to define such path variables manually.</li> </ul> -<h4><a class="mozTocH4" name="mozTocId538141"></a>Using Eclipse 4.6 to +<h4><a class="mozTocH4" name="mozTocId574781" />Using Eclipse 4.6 to develop plug-ins that work in Eclipse 4.5</h4> <p> It is also possible (and reasonable) to use Eclipse 4.6 to develop a plug-in intended to work in Eclipse 4.5 or earlier. Use the <b>Plug-in @@ -1556,7 +1441,17 @@ APIs, extension points, and plug-ins. (The above list of concerns do not apply since they affect the layout and interpretation of files in the plug-in <i>project</i> but none affect the actual deployed form of the plug-in.) </p> -<hr> +<h2 id="appendix"><a class="mozTocH2" name="mozTocId317294" />Appendix: +Execution Environment by Bundle</h2> +<!-- + Remember, the URL to appendix link must be full URL, since some may be + viewing this file, from a "file://" URL +--> +<p> See the table in the <a + href="https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#appendix">Eclipse +4.6 Project Plan Appendix</a> for the list of the minimum execution +environment (Java class library) requirements of each bundle. </p> +<hr /> <p>Sun, Solaris, Java and all Java-based trademarks are trademarks of Oracle Corporation. in the United States, other countries, or both.</p> <p>IBM is a trademark of International Business Machines Corporation in @@ -1568,16 +1463,6 @@ countries, or both.</p> in the U.S. and other countries.</p> <p>Other company, product, and service names may be trademarks or service marks of others.</p> -<p>(c) Copyright Eclipse Contributors 2009, 2015</p> -<h2 id="appendix"><a class="mozTocH2" name="mozTocId530462"></a>Appendix: -Execution Environment by Bundle</h2> -<!-- - Remember, the URL to appendix link must be full URL, since some may be - viewing this file, from a "file://" URL ---> -<p> See the table in the <a - href="https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#appendix">Eclipse -4.6 Project Plan Appendix</a> for the list of the minimum execution -environment (Java class library) requirements of each bundle. </p> +<p>(c) Copyright Eclipse Contributors 2009, 2016</p> </body> </html> |