We focus our testing on a handful of popular combinations of operating system and Java Platform; these are our reference platforms. Eclipse undoubtedly runs fine in many operating environments beyond the reference platforms we test. However, since we do not systematically test them we cannot vouch for them. Problems encountered when running Eclipse on a non-reference platform that cannot be recreated on any reference platform will be given lower priority than problems with running Eclipse on a reference platform.
As stated above, 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.
The Eclipse SDK is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages, are externalized. The English strings are provided as the default resource bundles. Downward contract compatibility is not supported. There is no guarantee that compliance with Eclipse SDK 3. Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK 3.
This means that source files written to use Eclipse SDK 3. Downward source compatibility is not supported. This means that workspaces and projects created with Eclipse SDK 3. This includes both hidden metadata, which is localized to a particular workspace, as well as metadata files found within a workspace project e.
Individual plug-ins developed for Eclipse SDK 3. User interface session state may be discarded when a workspace is upgraded. Downward workspace compatibility is not supported. A workspace created or opened by a product based on Eclipse 3. Visible metadata files created or overwritten by Eclipse 3. Non-compliant usage of API's : 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, are considered implementation details which may vary between operating environment and are subject to change without notice.
Client plug-ins that directly depend on anything other than what is specified in the Eclipse SDK API are inherently unsupportable and receive no guarantees about compatibility within a single release much less with earlier releases. The workaround is to install Eclipse in a directory whose path does not contain invalid characters. The Sun VM may hang indefinitely during class loading if it runs out of permanent generation memory.
See the section Running Eclipse for details on addressing this VM problem. Unfortunately, the GCJ runtime environment is not an environment that is often tested on by Eclipse developers. 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:. The About 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. To run Eclipse with an alternate Java runtime environment, the path to the Java virtual machine's binary must be identified. An example of the terminal's output is shown below:. Once the path to the virtual machine's binary has been identified, try running Eclipse with the following command:. 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. An example of its content is presented below:. Note that every argument must be on its own line. More information about the eclipse. If problems persists after downloading an installation of Eclipse from eclipse. The crash usually occurs within a VM CompilerThread when attempting to compile the method org. This problem has been addressed in Sun Java 6 update 11, so the simplest resolution is to obtain the latest JRE release for your platform.
To work around the issue you can exclude the method org. This VM argument can be placed in the eclipse. 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". New plug-ins can be installed into the system by unzipping them into the plugins directory. However this is not recommended, and the dropins directory should be used for this purpose instead.
Note that unzipping a different version of a plug-in that is already installed will have no effect. To change the version of a plug-in installed in your system, you need to either perform an update, or install a feature patch. If you have an old config. This is because the id of the standard Eclipse product changed. Users in shared install scenarios may end up in this situation as previous builds of Eclipse automatically generated config.
The work around is either to delete the local config. 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 ClassNotFoundException. As a workaround, do the following:. If you set the context class loader for the current thread, you are 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.
If Plugin. Only simple bookkeeping tasks should be performed in Plugin. 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 Export-packages bundle manifest header. To work around this you should ship your plug-in with a bundle manifest.
If you are running in debug mode on Mac OS, the default location for the. 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. 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 contained in plug-ins. In this case the application classloader is used. 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 must be provided in a separate JAR that is contributed to the org. This ensures that the Ant tasks and types are loaded by the special Ant class loader and not by a plug-in classloader. Several aspects of Ant and its use of global Java resources such as System.
Since there are differences when running Ant from the commandline and within Eclipse, some extra steps may be needed to have XDoclet support function correctly within Eclipse. Problems may occur creating XDoclet subtasks. The workarounds and full discussion can be found in bug report. Code completion provided by the Ant editor does not respect the user-specified version of org. Code completion proposals are mostly based on Ant 1. If you rename an existing external tool builder that is configured to run during auto-builds, you will get the following error: Errors during build.
The builder launch configuration could not be found. The workaround is to first disable the builder for auto-builds and then rename the builder. See bug for a possible workaround. Due to a bug in Ant 1. Embedded usage of Ant builds, such as plug-in export will also fail.
See bug for possible workarounds. In Ant 1. 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 bug For more information on tasks that require additional bundles please refer to the Ant 1.
The extension-point feature added in Ant 1. See bug for more details. If no supported browser can be found, Welcome falls back to its Forms-based implementation, which has a different simpler appearance.
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. Windows High Contrast settings are not consistently picked up by Internet Explorer when they are set from the Accessibility Options utility as opposed to when they are set using the predefined schemes.
On Windows XP, it is recommended to set High Contrast as follows: Right click the desktop, chose properties, select Windows Classic style from the Windows and buttons drop down on the Appearance tab, and choose your scheme for example High Contrast Black from Color Scheme drop down. 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.
Workspaces that are currently using the Eclipse 2. Currently there is no way on the Max or Linux platforms to define the height for controls contributed to toolbars, nor will those platforms respect the size returned by the control's computeSize method.
If you encounter this issue there is currently no truly viable workaround. Wed, 22 June Vladimir Messages: 7 Registered: June Still the same for me Tested it on the actual Indigo release. Has anybody found a solution? Vladimir Report message to a moderator. Thu, 23 June Borislav Messages: 3 Registered: June With update manager you can install only prior versions to 2. To solve the problem get the required version manually from the download section for qvt and gmf and install them trough unziping.
That solved the problem for me. Thanks for your reply, Borislav. I've done as proposed und installed manually gmf-sdk Anything i've done wrong? Hi all, I'm sorry but I don't really understand your issue. Can you please re-explain it? We'll try to get it released ASAP, but there is still a blocking bug that needs to be fixed.
Regards, Mickael Report message to a moderator. Sat, 25 June I have downloaded the mentioned versions of archives and unzipped them into the fresh eclipse indigo installation. I think, i will try to start with the "old" eclipse version with gmf and then try to port the project to the working release of an actual one.
Regards Vladimir Report message to a moderator. Wed, 06 July Karthikeyan Missing name Messages: 47 Registered: July Hi, I am trying to create new gmf project in Eclipse Helios or Indigo, but create new gmf project wizard not available in both of helios and Indigo.
Is the gmf latest plugin available for helios or Indigo? If so kindly reply me and also tell me the latest GMF release version. Regards, Karthikeyan Report message to a moderator. 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. Typically, in Gnome Linux installs running with 8-bit visuals i.
This may mean that Eclipse is unable to allocate the default widget background color, causing it to display a white background. The functionality, however, is otherwise unaffected. When typing Japanese text, the conversion to Kanji must be done one ideogram at a time. On some versions of Debian, Eclipse key bindings may stop working. In this context the only way to make the key bindings work again is to restart Eclipse. When running on the IBM Java 5. The command line for launching Eclipse with this vm should be: eclipse -vmargs -Dosgi.
Eclipse fails to create a lock file with reason "No locks available". To launch eclipse you must disable file locking using the osgi. For example, you could launch eclipse as follows: eclipse -vmargs -Dosgi. Strings on wrapping Controls may not appear correctly in some locales on RHEL5 as a result of a bug in Pango version 1. This problem can be fixed by upgrading the installed Pango library to a version that is newer than 1.
When the orientation of characters under the left and right edges of the block selection rectangle are not the same, the actual selection ranges in memory differ from the visual representation of the selection.
The workaround for these cases is to specify Java property org. An easy way to set this property is to specify VM argument -Dorg. On modern Linux distributions with a GTK version greater than 2. These problems seem to be caused by low-level bugs in the interactions between GDK and X. The workaround for this problem is to specify Java property org. On recent Ubuntu Linux distributions that feature the Unity desktop, the menus from the workbench will not appear in the top desktop menu bar.
They will continue to appear in the shell. The following are known problems with the CVS repository provider only, and do not apply to other repository providers. 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 stable 1. X builds of the CVS server, and should be compatible with future releases in that stream unless text message formats change the last tested server was 1.
As for the 1. 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.
CVS now uses the Platform proxy settings. 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. Eclipse sometimes performs multiple commands within a single connection to the server.
This may cause problems with CVS servers that are running server scripts in response to certain commands. 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. 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.
Another involves Eclipse not properly reading the stderr output of the external communications tool. New in 3. However, for backwards 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. When folders containing build output are shared they may get improperly marked as dirty when build output is generated. GNOME applications can make use of proxy settings defined in this environment.
If set, Eclipse will use it prior to proxy settings declared using env variables. This feature is disabled by default, to enable it launch Eclipse with "-Dorg. That is,. 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.
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. 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 Feature patches can only be installed from update sites designed for Eclipse 3.
Specifically, the update site must have the necessary metadata for Equinox p2 a content. This data can be generated by building an update site using Eclipse 3. See the help topic Generating p2 metadata for more details on running the p2 metadata generator bug Known problems with the Java debugger appear below in the JDT section.
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.
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. 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. Creating and applying refactoring scripts sometimes fails with Sun 6.
A workaround is to use a J2SE 5. Exception breakpoints can be configured with location filters inclusive and exclusive. When an unchecked exception is configured to not suspend execution in a specific class, execution will still suspend when the user preference to suspend on uncaught exceptions is on.
Most class libraries do not properly support the creation of a system process via java. This limitation means the debugger cannot launch applications when the command line it generates contains GB characters. Since Javadoc is created using the Javadoc executable provided with the JDK, generating Javadoc fails if the package or class name contains GB characters. If a debug session suspends on a java. StackOverflowError exception due to an exception breakpoint , the debugger may not be 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. The debugger uses threads in the target JVM to perform evaluations both explicit evaluations that the user requests, and implicit evaluations such as toString invocations in the Variables view.
The Java Debug Interface JDI requires that the thread in which an evaluation is performed be suspended by a user event that is, a breakpoint or step request. Evaluations cannot be performed on threads suspended by the suspend action. As well, when a breakpoint is configured to suspend the JVM rather than just the individual thread, the threads which did not encounter the breakpoint are not in a valid state to perform an evaluation.
When an evaluation is attempted in a 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". Hot code replace is supported on JDK 1. 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. Note that hot code replace and stepping on JDK 1.
When a snippet is run in the scrapbook which directly or indirectly calls System. VMDisconnectedException being displayed in the scrapbook editor. Terminating a scrapbook page while it is performing an evaluation results in a com. Java 6 annotation processors are supported in the batch compiler and in the IDE. By design, Java 6 processors are only executed during a build, not while editing.
Java 5 annotation processors are supported in the IDE only. Java 5 processors can be executed while editing, as well as during a build. Slow annotation processors can cause a slowdown of the editing experience. Java indexing encounters problems when a folder is used both as a source folder in a project and as a class folder in another project. Hence, when this peculiar setup is used, the Java Search might miss matches located in such a folder.
To avoid this kind of problem, it is strongly advised to use different folders for sources and binary classes. 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. 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 org.
0コメント