diff options
| author | David Williams | 2015-06-05 03:03:50 +0000 |
|---|---|---|
| committer | David Williams | 2015-06-05 03:04:13 +0000 |
| commit | e24c2f440a18cdef6ee48762f05f5c947e163056 (patch) | |
| tree | d391baf00d0cb2cb0fc96fe40a9741e872483aaf | |
| parent | c9fb3970e38f14057e00bd50d3ad801dfc89dfa0 (diff) | |
| download | eclipse.platform.releng-e24c2f440a18cdef6ee48762f05f5c947e163056.tar.gz eclipse.platform.releng-e24c2f440a18cdef6ee48762f05f5c947e163056.tar.xz eclipse.platform.releng-e24c2f440a18cdef6ee48762f05f5c947e163056.zip | |
Bug 468491 - Need to update web readme.html/php for 4.5 (Mars)
Synchronizing with "web version". It is equivilant to what was "shipped"
in Mars (as of RC4) ... but converted to HTML 5 and made to co-exist
with Solstice theme.
| -rw-r--r-- | features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html | 246 |
1 files changed, 126 insertions, 120 deletions
diff --git a/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html b/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html index b2bea404..c147343c 100644 --- a/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html +++ b/features/org.eclipse.rcp/rootfiles/readme/readme_eclipse.html @@ -1,34 +1,7 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> +<!DOCTYPE html> +<html xmlns="http://www.w3.org/1999/xhtml"> <head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> -<style type="text/css"> - table.platforms { - border-width: 1px; - border-spacing: 0px; - border-style: solid; - border-collapse: separate; - } - table.platforms th { - border-width: 1px; - padding: 3px; - border-style: inset; - border-color: black; - background-color: #B9A9FF; - } - table.platforms td { - border-width: 1px 1px 1px 1px; - padding: 3px 3px 3px 3px; - border-style: inset inset inset inset; - border-color: gray gray gray gray; - } - table.platforms tr.c0 td { - background-color: #FDFDFD; - } - table.platforms tr.c1 td { - background-color: #F4EEFF; - } -</style> +<meta charset="UTF-8" /> <title>Eclipse Project Release Notes 4.5</title> </head> <body> @@ -37,10 +10,10 @@ <p>Release 4.5.0<br/> Last revised June 3, 2015</p> -<p align="left"><strong>This software is OSI Certified Open Source Software.<br/> +<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> <blockquote> - <p align="left"><a href="#TargetOperatingEnvironments">1. Target Operating + <p style="text-align:left;"><a href="#TargetOperatingEnvironments">1. Target Operating Environments</a><br/> <a href="#Compatibility">2. Compatibility with Previous Releases</a><br/> @@ -49,9 +22,9 @@ OSI Certified is a certification mark of the Open Source Initiative. </stro <a href="#Upgrading">5. Upgrading a Workspace from a Previous Release</a><br/> <a href="#InteroperabilityWithPreviousReleases">6. Interoperability with Previous Releases</a><br/> - <a href="#appendix">Appendix 1: Execution + <a href="#appendix">Appendix 1: Execution Environment by Bundle</a><br/> - + </p> </blockquote> @@ -82,8 +55,42 @@ OSI Certified is a certification mark of the Open Source Initiative. </stro <p>Eclipse 4.5 is tested and validated on the following reference platforms (this list is updated over the course of the release cycle):</p> -<center> - <table class="platforms"> +<div> +<!-- NOTE: we intentionally do not want <style> in <head> because then if we + wrap this HTML with a Solstice PHP theme, Solstice will ignore (or, replace) + any <style> that is in <head>. Thus, this allows us to use our own style for + table, with both plain HTML5 and Solstice wrapped PHP/HTML5. The 'scoped' attribute + means to apply this style only to things 'in' the container parent (the <div>) + and not whole document, and it is required for any <style> element not in <head>. --> +<style type="text/css" scoped> + table.platforms { + margin: 0 auto; + border-width: 1px; + border-spacing: 0px; + border-style: solid; + border-collapse: separate; + } + table.platforms th { + border-width: 1px; + padding: 3px; + border-style: inset; + border-color: black; + background-color: #B9A9FF; + } + table.platforms td { + border-width: 1px 1px 1px 1px; + padding: 3px 3px 3px 3px; + border-style: inset inset inset inset; + border-color: gray gray gray gray; + } + table.platforms tr.c0 td { + background-color: #FDFDFD; + } + table.platforms tr.c1 td { + background-color: #F4EEFF; + } +</style> + <table class="platforms"> <tr> <th>Operating System</th> <th>Version</th> @@ -233,7 +240,7 @@ OSI Certified is a certification mark of the Open Source Initiative. </stro <tr class="c0"> <td rowspan="1">Power 64-bit</td> </tr> - + <!-- ************ Mac ************** --> <tr class="c1"> <td rowspan="1">Apple Mac OS X</td> @@ -245,8 +252,7 @@ OSI Certified is a certification mark of the Open Source Initiative. </stro <td rowspan="1">Cocoa</td> </tr> </table> - </center> - +</div> <p>As stated above, <i>we expect that Eclipse works fine on other current Java VM and OS versions but we cannot flag these as reference platforms without significant community support for testing them.</i></p> @@ -275,7 +281,7 @@ OSI Certified is a certification mark of the Open Source Initiative. </stro <a href="http://wiki.eclipse.org/index.php/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.5 is upwards binary-compatible with Eclipse SDK 4.4 except in those areas noted in the <a href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_5_porting_guide.html" target="_top"> @@ -285,7 +291,7 @@ OSI Certified is a certification mark of the Open Source Initiative. </stro <a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs"> <em>Evolving 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.5 is upwards source-compatible with Eclipse SDK 4.4 except in the areas noted in the <a href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_5_porting_guide.html" target="_top"> @@ -295,7 +301,7 @@ OSI Certified is a certification mark of the Open Source Initiative. </stro SDK 4.5 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.5 is upwards workspace-compatible with earlier 3.x and 4.x versions of the Eclipse SDK unless noted. This means that workspaces and projects created with Eclipse SDK 4.4, 4.3, 4.2, .. 3.0 can be successfully @@ -312,7 +318,7 @@ OSI Certified is a certification mark of the Open Source Initiative. </stro a product based on Eclipse 4.5 will be unusable with a product based on an earlier version of Eclipse. Visible metadata files created (or overwritten) by Eclipse 4.5 will generally be unusable with earlier versions of Eclipse. </p> - + <p><strong>Non-compliant usage of API's</strong>: All non-API methods and classes, and certainly everything in a package with "internal" in its name or x-internal in the bundle manifest entry, @@ -359,19 +365,19 @@ OSI Certified is a certification mark of the Open Source Initiative. </stro <h4>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> - <li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 4.5 requires - at least a Java SE 7. Perhaps an older version of the VM is being found in - your path. To explicitly specify which VM to run with, use the Eclipse <tt>-vm</tt> - command-line argument. (See also the <a href="#RunningEclipse">Running Eclipse</a> + <li>As shown <a href="#TargetOperatingEnvironments">above</a>, Eclipse 4.5 requires + at least a Java SE 7. Perhaps an older version of the VM is being found in + your path. To explicitly specify which VM to run with, use the Eclipse <code>-vm</code> + command-line argument. (See also the <a href="#RunningEclipse">Running Eclipse</a> section below.)</li> <li> Running Eclipse on Gentoo Linux may result in the following error message: - <div style="margin-left: 40px;"> -<tt>* run-java-tool is not available for sun-jdk-1.6 on i686<br/>* IMPORTANT: some Java tools are not available on some VMs on some architectures</tt> + <div style="margin-left: 40px;scoped=true;"> +<code>* run-java-tool is not available for sun-jdk-1.6 on i686<br/>* IMPORTANT: some Java tools are not available on some VMs on some architectures</code> </div> If this occurs, start Eclipse by specifying a -vm argument, either -specify the path to a java vm or use: <tt>eclipse -vm `java-config</tt> +specify the path to a java vm or use: <code>eclipse -vm `java-config</code> --java` (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=176021">176021</a>)</li> <li>Eclipse must be installed to a clean directory and not installed over top of a previous installation. If you have done this then please re-install to a new @@ -387,7 +393,7 @@ configuration area and as a result of this problem, may erroneously detect the current configuration location as writable. The net result is that Eclipse will fail to start and depending on the circumstances, may fail to write a log file with any details. To work around this, we suggest users experiencing this -problem set their configuration area explicitly using the <tt>-configuration</tt> command +problem set their configuration area explicitly using the <code>-configuration</code> command line argument. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=67719">67719</a>)</li> </ul> @@ -415,7 +421,7 @@ environment is not an environment that is often tested on by Eclipse developers. <ul> <li>Eclipse does not start at all</li> <li>Eclipse throws a 'java.lang.ClassNotFoundException: org.eclipse.core.runtime.Plugin' that can be found in the logs (located in -workspace/.metadata/.log)</li> +workspace/.metadata/.log)</li> </ul> <p>The workspace's log file is a good place to check to identify whether GCJ is @@ -491,15 +497,15 @@ org.eclipse.platform<br/> eclipse.ini file can be found at <a href="http://wiki.eclipse.org/Eclipse.ini">http://wiki.eclipse.org/Eclipse.ini</a>.</p> <p>If problems persists after downloading an installation of Eclipse from -eclipse.org and using a supported Java runtime environment (a list of which may be found <a href="#TargetOperatingEnvironments">above</a>), -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>, +eclipse.org and using a supported Java runtime environment (a list of which may be found <a href="#TargetOperatingEnvironments">above</a>), +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> <h3 id="I-General-64bitJava">3.1.3 General - 64-bit Java HotSpot(TM) VM</h3> <p> -There is a known issue with the Java HotSpot(TM) 1.6.0 VM compiler which causes eclipse to +There is a known issue with the Java HotSpot(TM) 1.6.0 VM compiler which causes eclipse to crash (see Sun bug <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6614100">http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6614100</a>, and Eclipse bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=214092">214092</a>). The crash usually occurs within a VM CompilerThread when attempting to compile the method org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith. @@ -535,8 +541,8 @@ org.eclipse.platform<br/> </code> <p> -There have been reports of other classes that cause the compiler to crash. If all else fails you can -disable the compiler with the VM arg "-Xint". +There have been reports of other classes that cause the compiler to crash. If all else fails you can +disable the compiler with the VM arg "-Xint". </p> <h3 id="I-Platform">3.2 Platform</h3> @@ -585,7 +591,7 @@ code. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=5875">5875</a> <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 file then there may be problems in the automatic generation of the bundle manifest file. The packages -defined in the nested JAR may not be exported correctly in the <tt>Export-packages</tt> +defined in the nested JAR may not be 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> @@ -596,24 +602,24 @@ directory (like the eclipse.ini). (bug <a href="https://bugs.eclipse.org/bugs/sh <h4>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 as in a C +There may be issues when using a JNI implementation that uses FindClass +in a function where the JNIEnv pointer is not available, such as in a C callback (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=125250">125250</a>). The reason is that FindClass, in this case, uses the application class loader to find the class. If the desired class is in the classpath used for the application classloader -(e.g. defined by the VM argument -cp <classpath>), as it would typically be in +(e.g. defined by the VM argument -cp <classpath>), as it would typically be in a stand-alone application, there is no problem. However, under -Eclipse, the application classloader does not have access to classes -contained in plug-ins. Eclipse uses its own class loader to find classes +Eclipse, the application classloader does not have access to classes +contained in plug-ins. Eclipse uses its own class loader to find classes contained in plug-ins. </p> <p> -The proper plug-in class loader is used by FindClass in JNI functions which are -passed the JNIEnv pointer, but not when you have to use AttachCurrentThread to get the +The proper plug-in class loader is used by FindClass in JNI functions which are +passed the JNIEnv pointer, but not when you have to 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 +For example, the following will fail because AttachCurrentThread is used to get the JNIEnv pointer:</p> <pre> static JavaVM* jvm; // Global variable @@ -676,7 +682,7 @@ special Ant class loader and not by a plug-in classloader. (bug <a href="https:/ <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37070">37070</a>)</p> <h4>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. +<p>Code completion provided by the Ant editor does not respect the user-specified version of org.eclipse.ant.core plug-in or ANT_HOME. Code completion proposals are mostly based on Ant 1.6.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> @@ -703,12 +709,12 @@ See bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=187993">187993</a <h4>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 build will now properly report as failed. -In previous versions of Ant, the build would still report that it had suceeded even though it actually failed to run any of the tasks from additional bundles. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=344518">bug 344518</a>. +In Ant 1.8.x, if you try to use a task that requires additional libraries and you do not have the libraries on the Ant classpath, the build will now properly report as failed. +In previous versions of Ant, the build would still report that it had succeeded even though it actually failed to run any of the tasks from additional bundles. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=344518">bug 344518</a>. </p> <p> For more information on tasks that require additional bundles please refer to the <a href="https://archive.apache.org/dist/ant/RELEASE-NOTES-apache-ant-1.8.2.html">Ant 1.8.2 release notes</a> -and the <a href="http://ant.apache.org/manual/install.html#optionalTasks">Optional Tasks</a> section in the Ant manual. +and 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">3.2.3 Platform - User Assistance</h3> @@ -809,8 +815,8 @@ Workaround is to open the download progress-bar dialog by opening chrome://mozap (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=467203">467203</a>)</p> <h4>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 +<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>Eclipse plug-in based on the SWT Browser throws exception</h4> @@ -859,7 +865,7 @@ workbench at a breakpoint and pasting into the hosting Eclipse workbench. (bug < a time. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=226636">226636</a>)</p> <h4>Eclipse won't start (Linux GTK PPC only)</h4> -<p>Eclipse fails to create a lock file with reason "No locks available". +<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/> <code>eclipse -vmargs -Dosgi.locking=none</code> @@ -912,7 +918,7 @@ to 1.12.13. 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>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 @@ -957,7 +963,7 @@ This feature is disabled by default, to enable it launch Eclipse with <h4>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 + 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 </pre> @@ -969,10 +975,10 @@ means the server is using a self-signed certificate, or a certificate authentica an unknown third party.</p> <h4>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 only happens when the link file that configures the -extension location 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 +<p>A previously configured extension location may be temporarily removed if the install is moved or mounted +under a different path. This only happens when the link file that configures the +extension location 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-Platform-Debug">3.2.9 Platform - Debug</h3> @@ -1012,16 +1018,16 @@ 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>Breakpoints unreliable running Sun 1.6.0_14</h4> -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 +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>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 <b>not</b> suspend - execution in a specific class, execution will still suspend when the user preference +<p>Exception breakpoints can be configured with location filters (inclusive and + exclusive). When an unchecked exception is configured to <b>not</b> suspend + execution in a specific class, execution will still 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>Running Java programs with non-Latin-1 characters in package or class names</h4> @@ -1189,7 +1195,7 @@ 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>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> +<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> @@ -1211,9 +1217,9 @@ delete the metadata in <workspace>/.metadata/.plugins/org.eclipse.pde.core </p> <h4>Missing @since tag API Tools problems on interface fields containing @noreference tag</h4> -<p>The Eclipse platform 4.5 release will not allow the API Tools @noreference tag on interface fields. This was +<p>The Eclipse platform 4.5 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 @noreference restriction. The -tag was allowed in previous releases and this usage will now be considered an API change requiring a @since tag. +tag was allowed in previous releases and this usage will now be considered an API change requiring a @since tag. It is recommended that you create an API Tools filter for the missing @since tag problem. This filter can be removed as soon as the API baseline has been regenerated. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=402393">402393</a>) @@ -1233,17 +1239,17 @@ instructions for Mac OS X are listed <a href="#macosx">below</a>.</p> <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 additional plug-ins you are using, and -the number of files you will be working with, you could conceivably have to increase -this amount. +the number of files you will be working with, you could conceivably have to increase +this amount. Eclipse allows you to pass arguments directly to the Java VM using the -<code>-vmargs</code> command line argument, which must follow all other Eclipse +<code>-vmargs</code> command line argument, which must follow all other Eclipse specific arguments. Thus, to increase the available heap memory, you would typically use:</p> <blockquote> <p><code>eclipse -vmargs -Xmx<memory size></code></p> </blockquote> <p>with the <code><memory size></code> value set to greater than -"1024M" (1024 megabytes -- the default). +"1024M" (1024 megabytes -- the default). </p> <p> When using an Oracle VM below 1.8, you may also need to increase the size of the permanent @@ -1264,7 +1270,7 @@ memory on your machine will cause Java to "thrash" as it copies object back and forth to virtual memory, which will severely degrade your performance. </p> <h3>Selecting a workspace</h3> -<p>When the Workbench is launched, the first thing you see is a +<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 not specify otherwise, Eclipse creates the workspace in your @@ -1292,11 +1298,11 @@ when you next launch Eclipse.</p> <li>Select the shortcut and edit its Properties. In the Target: field append the command line arguments.</li> </ol> -<p>Opening this shortcut launches Eclipse. (You can drag the shortcut to the +<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">Mac OS X</h3> -<p>On Mac OS X, you start Eclipse by double clicking the Eclipse application. If you need to +<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 bundle: select the Eclipse application bundle icon while holding down the Control Key. This will present you with a popup menu. Select "Show Package Contents" in the popup menu. @@ -1312,19 +1318,19 @@ a copy of the Eclipse install if you want to open more then one workspace at the same time (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139319">139319</a>). </p> -<p>If you need to launch Eclipse from the command line, you can create a symbolic link such as "eclipse". +<p>If you need to launch Eclipse from the command line, you can create a symbolic link such as "eclipse". It should point to the eclipse executable inside the application bundle and takes -the same arguments as "eclipse.exe" on other platforms. +the same arguments as "eclipse.exe" on other platforms. </p> <p>On Mac OS X 10.4 and later, you may notice a slow down when working 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">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 this, after unzipping Eclipse distribution, run Eclipse once with the "-initialize" -option from an account that has a write access to the install directory. -See <a href=" http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fmulti_user_installs.html">shared installs</a> in Eclipse +<p>The startup speed of a shared install can be improved if proper cache information is stored in the shared +install area. To achieve this, after unzipping Eclipse distribution, run Eclipse once with the "-initialize" +option from an account that has a write access to the install directory. +See <a href=" http://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> <h2 id="Upgrading">5. Upgrading Workspace from a Previous Release</h2> @@ -1379,13 +1385,13 @@ list on start-up, or</li> </ul> <h3>Dropped in bundles may not resolve after upgrade</h3> -<p>If you have installed bundles by dropping them into the <tt>plugins</tt> -or <tt>dropins</tt> directory, they might no longer resolve when you upgrade +<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 the Eclipse Platform, -there are new versions of bundles included in the platform, and often a small +there are new versions of bundles included in the platform, and often a small number of removed bundles. This may cause your previously dropped in bundles to no longer resolve and run. It is always recommended that you install software -via the <tt>Help > Install New Software</tt> mechanism so you are made +via the <code>Help > Install New Software</code> mechanism so you are made aware of any install-time failure to resolve dependencies. </p> @@ -1430,33 +1436,33 @@ repository. Here's how things typically go awry:</p> <p>Here are some things to watch out for when sharing projects between Eclipse 4.5 and earlier releases:</p> <ul> - <li><b>Virtual folders</b> - + <li><b>Virtual folders</b> - Eclipse 4.5 supports a notion of <i>virtual folders</i> that did not exist in Eclipse 3.5 or earlier. If such virtual folders are created in 4.5, and the project is subsequently loaded into an Eclipse 3.5 or earlier workspace, these folders will not be recognized. Recommendation: avoid creating virtual folders where project compatibility with Eclipse 3.5 or earlier is required.</li> - <li><b>Resource filters</b> - + <li><b>Resource filters</b> - Eclipse 4.5 supports a notion of <i>resource filters</i> that did not exist in Eclipse 3.5 or earlier. If such filters are added to resources in 4.5, and the project is subsequently loaded into an Eclipse 3.5 or earlier workspace, these filters will not be recognized. Recommendation: avoid creating resource filters where project compatibility with Eclipse 3.5 or earlier is required.</li> - <li><b>Predefined path variables</b> - + <li><b>Predefined path variables</b> - Eclipse 4.5 supports a set of built in path variables that can be used as the basis - for linked resource locations. Such variables will not be defined automatically in + for linked resource locations. Such variables will not be defined automatically in 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>Using Eclipse 4.5 to develop plug-ins that work in Eclipse 4.4</h4> -<p>It is also possible (and reasonable) to use Eclipse 4.5 to develop a plug-in - intended to work in Eclipse 4.4 or earlier. Use the <b>Plug-in Development > - Target Platform </b>preference page to locate non-workspace plug-ins in an Eclipse - 4.4 install. This ensures that the code for your plug-in is being compiled and - tested against Eclipse 4.4 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 +<p>It is also possible (and reasonable) to use Eclipse 4.5 to develop a plug-in + intended to work in Eclipse 4.4 or earlier. Use the <b>Plug-in Development > + Target Platform </b>preference page to locate non-workspace plug-ins in an Eclipse + 4.4 install. This ensures that the code for your plug-in is being compiled and + tested against Eclipse 4.4 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/> @@ -1474,11 +1480,11 @@ of others.</p> <h2 id="appendix">Appendix 1: Execution Environment by Bundle</h2> -<!-- - Remember, the URL to appendix link must be full URL, since some may be +<!-- + 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_5.xml#appendix">Eclipse 4.5 Project Plan Appendix</a> +<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_5.xml#appendix">Eclipse 4.5 Project Plan Appendix</a> for the list of the minimum execution environment (Java class library) requirements of each bundle.</p> </body> |