[ubuntu] - Installation [Résolu]

Hum.. ça je peux pas te le dire. Quand tu me colle ta ligne, il faut que tu me mette l'invite de commande aussi, comme ça:

apatik@laptop:~$: ls -a
.bashrc
.bash_history
Desktop/
Documents/
...

Ta localisation est indiquée par ton invite (si tu l'a pas modifié). Mais tape donc ces deux lignes, et colle moi le résultat (je viens de percuter que je me suis planté au dessus dans une ligne..)

cd ~/phpeclipse
ls -a

Merci de ton intérêt pour la chose :
J'ai fait une impression écran de ce que tu ma demandé de faire
http://img144.imageshack.us/img144/5437/capturehc6.jpg

Je suis désolé, mais étant au boulot, je n'ai pas accès a tous les sites internet, et je ne peux donc pas voir ton image. Le mieux reste que tu colle le resultat ici.

ok voila ce que j'ai fait :

user@user-desktop:~$ cd~/phpeclipse
user@user-desktop:~/phpeclipse$ ls -a
.              artifact.xml      eclipse.ini    libcairo-swt.so   readme
..             configuration    .eclipseproduct     notice.html
about_files    dropins   epl-v10.html    p2
about.html     eclipse     features    plugins

Ok. Donc première chose, lire le readme (lisez moi)
cat readme
Puis tu me le montre :) (même si c'est du texte, entre balise code ;) )

j'avais bien essayer de lire ce fichier mais j'ai pas réussi a trouver ce que je cherchais. Est-ce que tu veut voir quelque chose particulier dans ce read me parce qu'il est un peu long ou je te le met entier ?

Normalement, il te donne la marche a suivre.
Mais tu peux essayer directement
./configuration
(c'est le nom du fichier qui est dans le dossier qu'on utilise)

j'ai fait ./configuration :

bash: ./configuration : est un répertoire

donc je donc suis rentré dans ce dossier et dedans il y a un fichier config.ini. Est-ce cela ?

Je pense pas. En même temps.. t'as pas de Makefile.. on dirais qu'il est déjà utilisable... Affiche moi le readme même si il est long..

J'ai mis mon read me ici http://cyberfuntv.free.fr/
Si tu peut aller sur ces sites.

Nope.. je peux pas (pas grave si c'est long :) ), On a une liste blanche de sites accessibles.. et il y a pas grand chose (oui ça pue.. :( ) Colle le ici :)

Voila le readme bonne lecture ^^ <code> 1. Target Operating Environments

In order to remain current, each Eclipse release targets reasonably current operating environments.

Most of the Eclipse SDK is "pure" Java code and has no direct dependence on the underlying operating system. The chief dependence is therefore on the Java Platform itself. Portions of the Eclipse SDK (including the RCP base, SWT, OSGi and JDT core plug-ins) are targeted to specific classes of operating environments, requiring their source code to only reference facilities available in particular class libraries (e.g. J2ME Foundation 1.0, J2SE 1.3 and 1.4, etc.).

In general, the 3.4 release of the Eclipse Project is developed on a mix of Java 1.4 and Java5 VMs. As such, the Eclipse Project SDK as a whole is targeted at both 1.4 and Java5 VMs, with full functionality available for 1.4 level development everywhere, and new Java5 specific capabilities available when running on a Java5 VM. Similarly, in cases where support has been added for Java6 specific features (e.g. JSR-199, JSR-269, etc.) Java6 VMs are required.

Appendix 1 contains a table that indicates the class library level required for each plug-in.

There are many different implementations of the Java Platform running atop a variety of operating systems. We focus Eclipse SDK 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, including those using Java6 VMs. 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.

The Eclipse SDK 3.4 is tested and validated on the following reference platforms
Reference Platforms
Microsoft Windows Vista, x86-32, Win32 running (any of):

* Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows
* IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b
* BEA JRockit 27.4.0, for Microsoft Windows

Microsoft Windows XP, x86-32, Win32 running (any of):

* Sun Java 2 Standard Edition 6.0 Update 4 for Microsoft Windows
* Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows
* IBM 32-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b
* BEA JRockit 27.4.0, for Microsoft Windows
* Sun Java 2 Standard Edition 1.4.2_16 for Microsoft Windows
* IBM 32-bit SDK for Windows, Java 2 Technology Edition 1.4.2 SR10

Red Hat Enterprise Linux 5.0, x86-32, GTK running (any of):

* Sun Java 2 Standard Edition 5.0 Update 14 for Linux x86
* IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b
* BEA JRockit 27.4.0, for Linux x86
* Sun Java 2 Standard Edition 1.4.2_16 for Linux x86
* IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 1.4.2 SR10

SUSE Linux Enterprise Server 10, x86-32, GTK running (any of):

* Sun Java 2 Standard Edition 5.0 Update 14 for Linux x86
* IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition 5.0, SR6b

Microsoft Windows Vista, x86-64, Win32 running (any of):

* Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows (AMD64/EM64T)
* IBM 64-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b

Microsoft Windows XP Professional x64 Edition, x86-64, Win32 running (any of):

* Sun Java 2 Standard Edition 5.0 Update 14 for Microsoft Windows (AMD64/EM64T)
* IBM 64-bit SDK for Windows, Java 2 Technology Edition 5.0, SR6b

Red Hat Enterprise Linux 4.0 update 2, x86-64, GTK running:

* Sun Java 2 Standard Edition 5.0 Update 14 for Linux x86_64

Sun Solaris 10, SPARC, GTK running:

* Sun Java 2 Standard Edition 5.0 Update 14 for Solaris SPARC

HP-UX 11i v2, ia64, Motif 2.1, GTK running:

* HP-UX Java 2 Standard Edition 5.0 Update 7 for Itanium

IBM AIX 5.3, Power, Motif 2.1 running:

* IBM 32-bit SDK, Java 2 Technology Edition 5.0, SR6b

Red Hat Enterprise Linux 5.0, Power, GTK running:

* IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 5.0, SR6b

SUSE Linux Enterprise Server 10, Power, GTK running:

* IBM 32-bit SDK for Linux on pSeries architecture, Java 2 Technology Edition 5.0, SR6b

Apple Mac OS X 10.5, Universal, Carbon running:

* Apple Java 2 Platform Standard Edition (J2SE) 5, service release 4

Because Java 1.4.2 and Java5 based platforms are used for most Eclipse development, those platforms are listed here. Although there are teams doing some Java 6 based development we have not included specific Java6 VMs, since they have not yet received the general level of testing we require. We expect that Eclipse will work fine on other current Java VMs running on window systems supported by SWT, but can not flag these as reference platforms without significant community support for testing them.

Similarly, although untested, the Eclipse SDK should work fine on other OSes that support the same window system. For Win32: NT, 2000, and Server 2003; SWT HTML viewer requires Internet Explorer 5 (or higher). For GTK on other Linux systems: version 2.2.1 of the GTK+ widget toolkit and associated libraries (GLib, Pango); SWT HTML viewer requires Mozilla 1.4GTK2. For Motif on Linux systems: Open Motif 2.1 (included); SWT HTML viewer requires Mozilla 1.4GTK2.

SWT is also supported on the QNX Neutrino operating system, x86 processor, Photon window system, and IBM J9™ VM. Eclipse 3.4 on Windows or Linux can be used to cross-develop QNX applications. (Eclipse 3.4 is unavailable on QNX because there is currently no 1.5 J2SE for QNX.)
Internationalization

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.

Latin-1 and DBCS locales are supported by the Eclipse SDK on all reference platforms; BIDI locales are supported by the Eclipse SDK everywhere but on Motif.

The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard, on Windows XP and 2000, Linux/GTK and the Macintosh.

German and Japanese locales are tested.
2. Compatibility with Previous Releases
Compatibility of Release 3.4 with 3.3

Eclipse 3.4 is compatible with Eclipse 3.3 (and, hence, with 3.2, 3.1 and 3.0).

API Contract Compatibility: Eclipse SDK 3.4 is upwards contract-compatible with Eclipse SDK 3.3 except in those areas noted in the Eclipse 3.4 Plug-in Migration Guide. Programs that use affected APIs and extension points need to be ported to Eclipse SDK 3.4 APIs. Downward contract compatibility is not supported. There is no guarantee that compliance with Eclipse SDK 3.4 APIs would ensure compliance with Eclipse SDK 3.3 APIs. Refer to Evolving Java-based APIs for a discussion of the kinds of API changes that maintain contract compatibility.

Binary (plug-in) Compatibility: Eclipse SDK 3.4 is upwards binary-compatible with Eclipse SDK 3.3 except in those areas noted in the Eclipse 3.4 Plug-in Migration Guide. Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK 3.4 are not usable in Eclipse SDK 3.3. Refer to Evolving Java-based APIs for a discussion of the kinds of API changes that maintain binary compatibility.

Source Compatibility: Eclipse SDK 3.4 is upwards source-compatible with Eclipse SDK 3.3 except in the areas noted in the Eclipse 3.4 Plug-in Migration Guide. This means that source files written to use Eclipse SDK 3.3 APIs might successfully compile and run against Eclipse SDK 3.4 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.

Workspace Compatibility: Eclipse SDK 3.4 is upwards workspace-compatible with Eclipse SDK 3.3 unless noted. This means that workspaces and projects created with Eclipse SDK 3.3, 3.2, 3.1 or 3.0 can be successfully opened by Eclipse SDK 3.4 and upgraded to a 3.4 workspace. This includes both hidden metadata, which is localized to a particular workspace, as well as metadata files found within a workspace project (e.g., the .project file), which may propagate between workspaces via file copying or team repositories. Individual plug-ins developed for Eclipse SDK 3.4 should provide similar upwards compatibility for their hidden and visible workspace metadata created by earlier versions; 3.4 plug-in developers are responsible for ensuring that their plug-ins recognize 3.3, 3.2, 3.1, 3.0, 2.1, and 2.0 metadata and process it appropriately. 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.4 will be unusable with a product based an earlier version of Eclipse. Visible metadata files created (or overwritten) by Eclipse 3.4 will generally be unusable with earlier versions of Eclipse.

Non-compliant usage of API's: All non-API methods and classes, and certainly everything in a package with "internal" in its name, 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. Refer to How to Use the Eclipse API for information about how to write compliant plug-ins.
3. Known Issues

3.1 General problems
3.1.1 Startup
3.1.2 GCJ
3.1.3 UNC Paths
3.1.4 64-bit Java HotSpot(TM) VM
3.2 Platform
3.2.1 Core
3.2.2 Ant
3.2.3 User Assistance
3.2.4 UI
3.2.5 Text
3.2.6 SWT
3.2.7 Team and CVS
3.2.8 Install/Update
3.2.9 Debug
3.2.10 Compare
3.3 Java development tools (JDT)
3.4 Plug-in Development Environment (PDE)

Note: Bug numbers refer to the Eclipse project bug database at http://bugs.eclipse.org/bugs/
3.1 General problems
3.1.1 General - Startup
Installation/Configuration issues that can cause Eclipse to fail start

Here are some common problems that can cause Eclipse not to start:

* As shown above, Eclipse 3.4 requires at least a 1.4.2 VM. Perhaps an older version of the VM is being found in your path. To explicitly specify which VM to run with, use the Eclipse -vm command-line argument. (See also the Running Eclipse section below.)
* Running Eclipse on Gentoo Linux may result in the following error message:
* run-java-tool is not available for sun-jdk-1.6 on i686
* IMPORTANT: some Java tools are not available on some VMs on some architectures
If this occurs, start Eclipse by specifying a -vm argument, either specify the path to a java vm or use: eclipse -vm `java-config --java` (bug 176021)
* 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 directory. If your workspace is in a child directory of your old installation directory, then see the instructions below on "Upgrading Workspace from a Previous Release".
* Java sometimes has difficulty detecting whether a file system is writable. In particular, the method java.io.File.canWrite() appears to return true in unexpected cases (e.g., using Windows drive sharing where the share is a read-only Samba drive). The Eclipse runtime generally needs a writable 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 -configuration command line argument. (bug 67719)

Invalid characters in install directory prevents Eclipse from starting

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 contain invalid characters. (bugs 3109 and 17281)
Hanging during class loading when out of permanent generation memory

The Sun VM 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 Running Eclipse for details on addressing this VM problem.
3.1.2 General - GCJ

GCJ is an effort by the GCC team to provide an open source Java compiler and runtime environment to interpret Java bytecode. Unfortunately, the GCJ runtime environment is not an environment that is often tested on by Eclipse developers.

The most common problems surrounding GCJ are:

* Eclipse does not start at all
* Eclipse throws a 'java.lang.ClassNotFoundException: org.eclipse.core.runtime.Plugin' that can be found in the logs (located in workspace/.metadata/.log)

The workspace's log file is a good place to check to identify whether GCJ is being used or not. Every Eclipse log session should be prepended with information about the runtime environment that was used to run Eclipse. The log may include something like the following:
java.fullversion=GNU libgcj 4.2.1 (Debian 4.2.1-5)

If Eclipse does start, one can check which runtime environment is being used to run Eclipse by going to 'Help > About Eclipse SDK > Configuration Details'. 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.org website.
Eg: Build id: M20070212-1330 (Ubuntu version: 3.2.2-0ubuntu3)

The two most common workarounds are:

* download the Eclipse binary from eclipse.org directly
* run Eclipse using an alternate Java runtime environment

To download Eclipse, try one of the links below:

* http://www.eclipse.org/downloads/
* http://download.eclipse.org/eclipse/downloads/

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 3.4.0 of the Eclipse SDK packaged for 32-bit and 64-bit processors.

eclipse-SDK-3.4-linux-gtk.tar.gz (32-bit)
eclipse-SDK-3.4-linux-gtk-x86_64.tar.gz (64-bit)

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:
searching for compatible vm...
testing /usr/lib/jvm/java-7-icedtea...not found
testing /usr/lib/jvm/java-gcj...found

Once the path to the virtual machine's binary has been identified, try running Eclipse with the following command:
./eclipse -vm /path/to/jre/bin/java

For an actual example, it might look something like the following:
./eclipse -vm /usr/lib/jvm/sun-java-6/bin/java
./eclipse -vm /opt/sun-jdk-1.6.0.02/bin/java

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:
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vm
/opt/sun-jdk-1.6.0.02/bin/java
-vmargs
-Xms40m
-Xmx512m

Note that every argument must be on its own line. More information about the eclipse.ini file can be found at http://wiki.eclipse.org/Eclipse.ini.

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 above), you can seek further assistance through the newsgroups, the IRC channel, and/or bugzilla.
3.1.3 General - UNC Paths

Eclipse 3.4.0 does not properly handle installation in a directory using Universal Naming Convention (UNC) paths. Limited uses of the platform will work in this environment, but there are known bugs with starting workspaces on a UNC location, or upgrading software installed in a UNC location (bug 235629, bug 207103). The platform is not well tested in such an environment.
3.1.3 General - 64-bit Java HotSpot(TM) VM

There is a known issue with the 64-bit Java HotSpot(TM) 1.6.0 VM compiler which causes eclipse to crash (see Sun bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6614100, and Eclipse bug 214092). The crash usually occurs within a VM CompilerThread when attempting to compile the method org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith.

To work around the issue you can exclude the method org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith from being compiled with the following VM argument:
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith

This VM argument can be placed in the eclipse.ini file after the -vmargs line like the following:
-startup
plugins\org.eclipse.equinox.launcher_1.0.100.v20080509-1800.jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.100.v20080509-1800
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
-Xms40m
-Xmx256m

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".
3.2 Platform
3.2.1 Platform - Core
Installing plug-ins by unzipping them into the plugins directory

If you have installed new plug-ins and they aren't showing up when you run, then perhaps you unzipped them into your "plugins" directory and your configuration might need to be refreshed. This can be accomplished by starting Eclipse with the -clean command line argument.
XML files with UTF-8 byte order mark fail to have content type detected

Eclipse will fail to detect the proper content type for XML files that have a UTF-8 byte order mark if Crimson is the XML parser (as it is on Sun 1.4 JREs, but not on Sun 1.5 JREs). This problem will prevent actions normally available when files of the affected content types are selected from being presented to the user. The workaround is to ensure the default XML parser supports UTF-8 BOMs (such as Xerces does). (bug 67048)
No branding with old config.ini

If you have an old config.ini file and use it with a new Eclipse build, you may not get the correct product branding. 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.ini files in some cases. The work around is either to delete the local config.ini or update the eclipse.product line to read eclipse.product=org.eclipse.platform.ide.
Problems with classloaders in created threads

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:

1. Create a thread in which to run your code.
2. Send yourThread.setContextClassLoader(yourClassLoader); // you can find your classloader by grabbing a class it loaded (YourPluginClass.class.getClassLoader())
3. Run your code in the newly created thread.

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. (bug 8907)
Deadlock creating executable extension in Plugin.startup

If Plugin.startup 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 Plugin.startup code. (bug 5875)
Potential Problems Converting Plug-in Manifests

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. (bug 97689)
Location for Debug Options File on Mac OS

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 88782)
Configuration can become invalid when removing org.eclipse.update.configurator

When launching an Eclipse Application from within the Eclipse IDE it is possible to select the set of plug-ins that are included in the Eclipse Application. Removing the org.eclipse.update.configurator plug-in from the set of plug-ins to an existing configuration can cause the configuration to become invalid. This can result in extra plug-ins installed in the target application that are not resolved. To work around this, after the org.eclipse.update.configurator plug-in has been removed, the target configuration area should be cleared before launching. (bug 85835)
Issues with JNI that use FindClass

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 125250). 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 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 contained in plug-ins.

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.

For example, the following will fail because AttachCurrentThread is used to get the JNIEnv pointer:

static JavaVM* jvm; // Global variable

void myCallback(void) {
JNIEnv* env;
jvm->AttachCurrentThread((void**)&env, NULL);
// Fails if some/class is not in the application classloader:
jclass cls = env->FindClass("some/class");
jmethodID methodID = env->GetMethodID(cls, "methodName",
"(Ljava/lang/String;)V or whatever signature");
env->CallVoidMethod(callback, methodID, ...);
jvm->DetachCurrentThread();
}
}

A solution is to cache the method ID, for example:

static jmethodID mid; // Global variable

JNIEXPORT jint JNICALL JNI_OnLoad(JavaVM *vm, void *reserved) {
...
// Store the JavaVM pointer
jvm = vm;

// Find the class and store the method ID
// Will use the class loader that loaded the JNI library
jclass cls = env->FindClass(className"some/class");
if(!cls) goto ERR;

mid = env->GetMethodID(cls, "methodName",
"(Ljava/lang/String;)V or whatever signature");
if(!mid) goto ERR;
...
}

void myCallback(void) {
JNIEnv* env;
jvm->AttachCurrentThread((void**)&env, NULL);
env->CallVoidMethod(callback, mid, ...);
// Handle error ...
jvm->DetachCurrentThread();
}
}

3.2.2 Platform - Ant
UTF-8 encoded buildfiles with Byte Order Mark

UTF-8 encoded buildfiles with byte order marks will fail to be parsed correctly depending on the XML parser being used for the build. Therefore a valid buildfile will fail to build with an error message similar to: "BUILD FAILED: C:\workspace\bom.xml:1: Document root element is missing.". To succeed in building with these files, ensure to include Xerces jars on the Ant runtime classpath so that the Xerces parser is used to parse the XML. As well the context menu for these files in the Navigator or Package Explorer will not have the run shortcuts for Ant builds. (bug 67048)
Custom Ant tasks and Ant types must be separate from plug-in library JARs

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.eclipse.ant.core.antTasks or antTypes extension point (and not declared as a library in the plug-in's manifest). This ensures that the Ant tasks and types are loaded by the special Ant class loader and not by a plug-in classloader. (bug 34466).
Concurrent Ant builds not supported

Eclipse can run Ant in the same JVM as the rest of Eclipse. Several aspects of Ant and its use of global Java resources (such as System.out and System.err), make it unsafe to run more than one Ant build concurrently in the same JVM. (bug 24129).
Running certain Ant tasks cause memory leakage

Certain Ant tasks are known to leak memory. Please see the bug report for details, patches, and possible workarounds. (bug 24448)
Tasks that require input lock up workspace

As with using Ant from the command line, prompts for input from the console is not handled. This is not the same as making use of the <input> task, which works correctly within Eclipse. (bug 21748)
"version" property is always set when running Ant in the same VM as Eclipse

The Xalan libraries set system properties including a version property. These get set as properties within the Ant build and therefore the "version" property cannot be set within an Ant buildfile due to the immutable nature of Ant properties. This property will always be set to "2.4.1" for Ant builds in the same VM as Eclipse. (bug 45717)
XDoclet support from within Eclipse

Since there are differences when running Ant from the commandline and within Eclipse, some extra steps may be needed to have XDoclet support function correctly within Eclipse. Problems may occur creating XDoclet subtasks. The workarounds and full discussion can be found in bug report. (bug 37070)
Ant Editor code completion based on Ant 1.6.1

Code completion provided by the Ant editor does not respect the user-specified version of org.eclipse.ant.core plug-in or ANT_HOME. Code completion proposals are mostly based on Ant 1.6.1 with some updates to Ant 1.6.5 (bug 30886)
Eclipse can hang due to implementation of the Ant <property> task (Windows 9X only)

On Windows 9X, using:<property environment="env"/> will cause Eclipse to hang if the build occurs in the same VM as Eclipse. Running the build in a separate VM will hang the build but not Eclipse. (bug 44196)
Setting build loggers not supported when debugging Ant builds

When debugging Ant builds within Eclipse, setting -logger as a program argument will be ignored.
Renaming an External Tool builder set to run during auto-build will cause errors

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. Errors running builder "Integrated External Tool Builder" on project <PROJECT_NAME>. The builder launch configuration could not be found. The workaround is to first disable the builder for auto-builds and then rename the builder. (bug 118294)
Slow typing/saving of the Ant editor with imports that define numerous macrodefs

The Ant editor is slow on saving with buildfiles that have <import> declarations of buildfiles that have numerous <macrodef>s. See bugs 92640 and 125117 for possible workarounds
Failure to run Ant builds on non-Windows platforms if Eclipse installed in location with spaces in the path

Due to a bug in Ant 1.7.0, Ant builds will fail with an IllegalArgumentException if the Eclipse installation is in a location with spaces in the path. Embedded usage of Ant builds, such as plug-in export will also fail. See bug 187993 for possible workarounds
3.2.3 Platform - User Assistance
Welcome page not displayed properly (Linux/Unix)

The default Welcome implementation is HTML-based and requires a supported browser in order to work. If no supported browser can be found, Welcome falls back to its Forms-based implementation, which has a different (simpler) appearance. Consult the SWT FAQ for supported browsers and setting up your browser to work with eclipse.
Help browser tool bar buttons do not work for some documents

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 44216)
Help documents not displayed in a browser or very slow document loading (Windows only)
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.

1. In the Control Panel, open Internet Options, select the Connections tab and choose LAN Settings.
2. If your host was configured to use DHCP for IP assignment, make sure that the "Automatically detect settings" check box is cleared.
3. If you use a proxy server, ensure that the "Bypass proxy server for local addresses" is selected.
4. In "Advanced" settings for proxies, add "127.0.0.1;localhost" to the "Exceptions" if these addresses are not listed.
5. If you are using an automatic configuration script for proxy settings, and are not sure that the script is correct, clear the "Use automatic configuration script" check box.

If the above steps do not fix your problem, try changing the port and host properties on the Help > Help Server preference page. In general, setting host to localhost or 127.0.0.1 should work. Also, especially when running a firewall, you may want to specify port 80 or some other firewall-friendly value. (bugs 7036, 9418, 11394)
Working disconnected from the network (Windows only)
If you are experiencing problems when not connected to the network, you must install the loopback adapter from the Windows installation CD. (bug 831)
Using Internet Explorer in offline mode (Windows only)
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 Connect or deselect "Work Offline" in the Internet Explorer "File" menu to return the system behavior to normal.
Help topics not highlighted in High Contrast mode (Windows only)

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. (bug 28609)
Help browser displays a blank page

If you see a help launched with a blank page, and no errors displayed, it can be caused by a conflict between libraries in org.eclipse.tomcat plug-in and jars optionally installed in JRE jre/lib/ext directory. To fix the problem, ensure that the JRE used for running Eclipse does not contain any J2EE or Apache jars in the jre/lib/ext directory. (bug 63970)
3.2.4 Platform - UI
High contrast settings

Eclipse was tested for High Contrast using 1152 x 864 resolution in Windows XP High Contrast mode. You can select this mode by selecting Accessibility Options > Display > Use High Contrast from the Windows XP Control Panel menu.
Default text file encoding may be detected incorrectly (Windows XP/2000 only)

Note: the bug report associated with this problem has been fixed. If you run Eclipse with JDK 1.5 or greater you should not have to use the workaround stated below any longer. However, the problem still exists when running Eclipse with JDK 1.4.x or lower, so in this case the workaround is still required .

The "Text file encoding" value displayed in the Preferences dialog under "Editors" may be wrong on platforms running Windows XP (or 2000) when the user locale and system locale differ.

Example of the manifestation of the bug: A Japanese user using Japanese Windows 2000 works in New York, United States. The user has selected English (United States) as the user locale. The "Text file encoding" value displayed by Eclipse is incorrect: "Cp1252" (English). It should display the system locale "MS932" (Japanese).

Workaround: The user can modify the user locale so that user locale and system locale are identical. In the example above, this means the user should set Japanese as the user locale. Then restart Eclipse. The "Text file encoding" value will then be correct: "MS932" (Japanese).

For Windows XP:

* To check the system locale: Open the Control Panel. Go to Regional and Language Options. Switch to the Advanced tab. The system locale is specified in "Language for non-Unicode programs".
* To change the user locale: Open the Control Panel. Go to Regional and Language Options. The user locale can be modified by changing the language in "Standards and formats".

For Windows 2000:

* To check the system locale: Open the Control Panel. Go to Regional Options. Look up the items in the General tab, inside the "Language settings for the system" group. The system locale is the item marked as (Default).
* To change the user locale: Open the Control Panel. Go to Regional Options. The user locale can be modified by changing the location in "Settings for the current user".

(bug 20641)
Dirty state not tracked properly for OLE documents (Windows only)

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 2564)
OLE document crashes can cause Eclipse to also crash (Windows only)

If an OLE document crashes, Eclipse can crash, or the workbench menus can become inconsistent.
2.1 Presentation based workspaces incorrectly get new Min/Max behavior

Workspaces that are currently using the Eclipse 2.1 Presentation will incorrectly 'inherit' the new min/max behavior when opened with 3.3.

Workaround:

1. Go to the 'Preferences -> Appearance' page, change the current presentation to 'Default' and select apply
2. Change it back to the 2.1 Presentation, select 'OK' and 'Yes' to the restart prompt

When the workbench re-opens the old min/max behaviour will be restored.
Toolbars only containing contributed controls exhibit display errors on Mac/Linux

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. (bug 183003)
3.2.5 Platform - Text
None.
3.2.6 Platform - SWT
Eclipse plug-in based on the SWT Browser throws exception

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 Browser widget. Supported platforms and prerequisites are listed on the SWT FAQ item "Which platforms support the SWT Browser?".
Crash when using the file dialog (Windows XP with SP2 only)

With some versions of Synergy from Telelogic, Eclipse will crash when you try to open a file dialog. This is due to a problem with the CMExplorer.dll. The workaround is to upgrade to Synergy 6.4 (or higher) or to run regsvr32 /u CMExplorer.dll and reboot (note that this will disable Active CM). (bug 87798)
Opening File Dialog crashes eclipse (Vista only)

On Vista, launching eclipse using -vmargs -Xmx[any size] can crash eclipse when the FileDialog is opened. The workaround is to use the default heap size, i.e. do not use the -Xmx VM args. (bug 188317)
Internet Explorer sometimes freezes on PDF documents with Acrobat Reader 6 (Windows only)

With Acrobat Reader 6 or 7, some users have experienced an unresponsive user interface for up to two minutes when closing a browser which is displaying a PDF document. The workaround is to disable displaying PDF in the browser. In Adobe Reader select Edit > Preferences... > Internet and uncheck 'Display PDF in browser'. (bug 56184)
Crash while editing text (Windows XP with SP2 only)

Some users who have installed Service Pack 2 on Windows XP have experienced crashes while using editors in Eclipse. The workaround is to place a working version of Windows\System32\USP10.DLL in the Eclipse startup directory or uninstall Service Pack 2. (bug 56390)
Input Method broken (Motif only)

Some versions of RedHat Linux such as Fedora Core 3 and Enterprise Linux WS release 4 use a new technology called IIIM (Intranet/Internet Input Method Framework) to replace the old XIM (X input method). When running on these new systems, Eclipse will crash if you attempt to enter any DBCS character. The workaround is to use a XIM based input method such as chinput. This problem may be fixed in newer releases of RedHat. (bug 89722)
Eclipse does not start on Linux-Motif with Xinerama and a UTF-8 locale

The Linux-motif build of Eclipse does not launch properly when run on a computer with Xinerama (provides support for dual head monitors) and a UTF-8 locale. The workaround for this problem is to change the locale to a non-UTF-8 value, or to disable Xinerama. (bug 38843)
Eclipse hangs when pasting from an unresponsive application (GTK only)

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 44915)
Unable to drag data between applications in simplified Chinese locale (Motif only)

When configured for the simplified Chinese locale, it is not possible to drag data between applications running on the Motif window system. This is a known limitation of the Open Motif library. (bug 29777)
Crash when attempting to launch file browser (AIX Motif only)

There is a known AIX graphics bug affecting certain levels of AIX releases. Ensure that the AIX install includes the necessary service updates as described in the "Install notes/requirements for Eclipse on AIX" attachment to Eclipse bug report number 34524.
Available colors on 8-bit Linux (Linux only)

Typically, in Gnome Linux installs running with 8-bit visuals (i.e. 256 color mode), before the Eclipse application is started there are no free colors. 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.
IME-related crash (Linux Motif only)

When using Linux Motif and GB18030 IME "chinput", Eclipse can crash if the IME client window is left open when the parent window is disposed. (bug 32045)
IME converstion problem (Solaris GTK only)

When typing Japanese text, the conversion to Kanji must be done one ideogram at a time. (bug 226636)
Using IBM J9 VM (Photon and AIX)

On QNX Photon and IBM AIX, the SWT library will not be found when running with an IBM J9 1.5 VM. This is a bug in the IBM J9 class library in version 1.5. You can workaround this problem by adding the SWT library directory to your LD_LIBRARY_PATH environment variable.
gtk_init_check and X11 socket failure when using the IBM 1.4.2 JRE (GTK only)

Under RHEL 3.1 with the IBM 1.4.2 JRE and a large number of plugins, Eclipse may fail to launch with an exception from gtk_init_check along with this error:

_X11TransSocketOpen: socket() failed for local
_X11TransSocketOpenCOTSClient: Unable to open socket for local

A workaround is to set the environment variable JAVA_HIGH_ZIPFDS to a value of 500 before starting Eclipse. (bug 106396)
Key bindings can stop working on Debian (GTK+ only)

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.

The problem is that a focus issue exists in GTK+ 2.6.7 and earlier, for which SWT has a workaround. This workaround is incompatible with the GTK+ 2.6.7 fix, so a GTK+ version check is done at runtime to determine whether the workaround should be used or not. However, Debian backported the GTK+ focus fix into their libgtk+2.0 (2.6.4-2) package, so the SWT workaround and GTK+ fix are both incorrectly applied in this context.

To work around this problem, either get the Debian unstable version of GTK+, compile your own GTK+, or hack SWT's Shell.gtk_realize(int) and change the version that it checks. See SWT bug 107013 and GTK+ bug 109246 for more information.
Browser does not display applets (Windows and OS X)

The Browser widget cannot be used to display pages containing Java applets on Windows and OS X, as a result of crashes that occur when attempting to launch a second JVM for the applet that is in-process with the main process JVM. The workaround for clients wishing to display web pages with Java applets is to launch an external web browser to do so with org.eclipse.swt.program.Program (see bugs 59506 and 100622).
Eclipse hangs with earlier versions of Quicktime (Intel Mac OS X only)

Some users reported encountering system hangs while using Eclipse on Intel-based Macs. These hangs were traced to a problem in some versions of QuickTime, which has now been fixed. Therefore, Eclipse users on Intel-based Macs should use Quicktime's update facilities to ensure that their Quicktime version is at least 7.1.1. (bug 142892)
Typing in an editor crashes with IBM 1.5 VM (Linux GTK PPC only)

When running on the IBM Java 5.0 VM, Eclipse crashes while the user is typing in an editor. If using this VM you must disable the JIT with the -Xnojit vm argument to avoid the crashes (see bug 116730). The command line for launching Eclipse with this vm should be:
eclipse -vmargs -Dosgi.locking=none -Xnojit
Eclipse won't start (Linux GTK PPC only)

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:
eclipse -vmargs -Dosgi.locking=none
SWT_AWT bridge doesn't work (Mac OSX only)

In order to use the SWT_AWT bridge on the Mac, OS X jre version 1.5.0 Release 5 (or greater) must be used.
Eclipse printing is disabled or Eclipse hangs when opening editor (GTK only)

In order to print from eclipse on GTK, you need to have GTK+ version 2.10 or later. In addition, at least two print backends must exist on the machine: file and lpr. Assuming a that GTK was installed in /usr, the installed backends can be viewed at /usr/lib/gtk-2.0/2.10.0/printbackends.
SWT cannot be used with OS X JRE version 1.6 (Mac OSX only)

OS X JRE version 1.6 assumes that pointers have a size of 64 bits, but SWT's Carbon port only uses 32-bit pointers, so SWT and Eclipse cannot be used with OS X JRE version 1.6. The workaround is to use an earlier supported version of the OS X JRE.
Browser.setText() cannot be used with beta versions of Firefox 3.0/XULRunner 1.9

As a result of a late interface change in the Firefox 3.0/XULRunner 1.9 development stream, most beta versions of these applications cannot be used by the Browser if its setText() API is used. This problem can be fixed by upgrading to the final release versions of these applications. (bug 235020)
Strings may be truncated or incorrectly wrapped on RHEL5 (Linux GTK only)

Strings on wrapping Controls may not appear correctly in some locales on RHEL5 as a result of a bug in Pango version 1.14.x. This problem can be fixed by upgrading the installed Pango library to a version that is newer than 1.14.x. (bug 231951)
3.2.7 Platform - Team - CVS

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 Eclipse CVS FAQ.
CVS server compatibility

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 stable 1.11.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.11.22). As for the 1.12.X feature releases of CVS, the Eclipse CVS client has been tested with builds up 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.
SSH2 proxy settings lost upgrading to 3.3

CVS now uses the Platform proxy settings. As a result, any CVS proxy settings will be lost and must be re-entered on the General>Network Connections preference page.
Connection cannot be found after initially missing

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 9295)
"Received broken pipe signal" error from server

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. (bugs 23575 and 23581)
"Terminated with fatal signal 10" error from server

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 15724)
"Unknown response" error using ext connection method

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 adds CRs to the communications channel (bug 21180). Another involves Eclipse not properly reading the stderr output of the external communications tool. (bug 11633)
A disabled CVS capability may not be auto-enabled in existing workspaces

New in 3.0 is the ability to disable capabilities and the CVS support in Eclipse can be disabled. 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. (bug 66977)
Builder output files may appear as changed

When folders containing build output are shared they may get improperly marked as dirty when build output is generated.
3.2.8 Platform - Install/Update
Manually installing features and plug-ins on a FAT file system (Windows only)

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,

eclipse.exe -clean

Connecting to untrusted sites using https

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.
Removing a link file does not uninstall the corresponding extension location

If you have an extension location in an Eclipse-based application that is connected to your configuration via a link file, the extension is not removed when the link is deleted. The workaround is to move or delete the extension location, and restart the platform with the -clean command line argument. You can then restore or move back the extension location content to its original location (bug 232094).

Extension location is lost if the install path changes

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 95403).
3.2.9 Platform - Debug

None. (Known problems with the Java debugger appear below in the JDT section.)
3.2.10 Platform - Compare

None.
3.3 Java development tools (JDT)
Multiple regions formatting in a given source snippet
In version 3.4, the new API method org.eclipse.jdt.core.formatter.CodeFormatter.format(int, String, IRegion[], int, String) has been added to allow the formatting of several regions in a source snippet with a single pass.
Even if specified, this method does not currently accept comments of the following kinds:

* org.eclipse.jdt.core.formatter.CodeFormatter#K_SINGLE_LINE_COMMENT
* org.eclipse.jdt.core.formatter.CodeFormatter#K_MULTI_LINE_COMMENT
* org.eclipse.jdt.core.formatter.CodeFormatter#K_JAVA_DOC

This will be fixed in a future release (bug 233967).
Searching for constant field references

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 12044)
Cut, copy, paste not working for linked resources in views showing Java elements

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 34568)
Java working sets not working correctly for elements from JRE system library container

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 35395)
Cannot generate Javadoc for packages with GB18030 characters in the name

Most class libraries do not properly support the creation of a system process (via java.lang.Runtime.exec(...)) when the specified command line contains GB18030 characters. Since Javadoc is created using the Javadoc executable provided with the JDK, generating Javadoc fails if the package or class name contains GB18030 characters. (bug 32215)
Side effects of Step into Selection and Run to Line

The actions "Step into Selection" and "Run to Line" optimistically set breakpoints on the line the user has chosen to step into or run to. However, the debugger can not determine if or when execution will ever reach the chosen line. The breakpoints set by the underlying implementation are not visible to the user and can cause execution to suspend unexpectedly at a later time, when the associated line is actually executed. (bug 51507)
Default locale initialization incorrect

The default locale is generally initialized from the settings in the operating system when a target VM is launched. However, when using javaw.exe on JDK1.4.2, Windows XP, the default locale is incorrectly initialized to en_US, no matter what the operating system settings are. (bug 65945)
Suspend on uncaught exception overrides exception breakpoint location filters

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. (bug 66770)
Running Java programs with non-Latin-1 characters in package or class names
You get a java.lang.NoClassDefFoundError 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 4181)
Cannot run or debug class in a project with GB18030 characters in project name

Most class libraries do not properly support the creation of a system process (via java.lang.Runtime.exec(...)) when 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 32206)
Cannot detect installed JRE with GB18030 characters in path name

Automatic JRE detection fails when the JRE is stored in a directory containing GB18030 characters in its name. (bug 33844)
Unable to debug stack overflows

If a debug session suspends on a java.lang.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. (bug 19217)
Evaluation limitation

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". (bug 34440)
Missing debug attributes
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, "rt.jar") are compiled without complete debug attributes, and thus local variables and method arguments for those classes are not visible in the debugger.
Using Hot Code Replace

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.

Note that hot code replace and stepping on JDK 1.4.0 VMs was unreliable. The underlying VM problems were fixed in JDK 1.4.1, and later.
Scrapbook
Setting a breakpoint inside a scrapbook page is not supported.

When a snippet is run in the scrapbook which directly or indirectly calls System.exit(int), the evaluation cannot be completed, and will result in a stack trace for a com.sun.jdi.VMDisconnectedException being displayed in the scrapbook editor.

Terminating a scrapbook page while it is performing an evaluation results in a com.sun.jdi.VMDisconnectedException being displayed in the scrapbook editor.
Debugging over slow connections
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 Java > Debug preference page. Changing the timeout value only effects subsequently launched VM, not VMs that are already running.
Updating of inspected values
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).
Stepping over native methods that perform I/O
When the debugger steps over native methods that perform I/O to System.out or System.err, the output may not appear immediately unless the native performs a flush on the output buffer.
VM and process termination running on IBM 1.3 JVM on Linux (Linux only)
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 Terminate and Remove 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 1631)
Memory View (Linux only)
The feature to automatically load segments of memory while scrolling in the Memory view does not work on Linux. Instead the user must use the "Next Page" and "Previous Page" actions to manually load memory segments (bug 74559)
Java 6 Annotation Processing
Java 6 annotation processors are supported in the batch compiler and in the IDE, with some limitations. Java 6 processors are only executed during a build, not while editing (bug 188558). Some methods in the processing API are unimplemented when compiling within the IDE, and will throw UnsupportedOperationException.
3.4 Plug-in Development Environment (PDE)
Feature manifest editor does not preserve all comments

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 59502)
PDE will not unzip source zips of some plug-ins

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.apache.ant, org.eclipse.core.runtime.compatibility.registry, org.eclipse.osgi.util and org.eclipse.osgi.services. This is because

J'ai lu en diagonale, apparament, il n'y a rien a faire, le prog est utilisable. Si tu sais t'en servir, tu n'a qu'a utiliser
./eclipse
Sinon, cherche le manuel sur google. Mais la prochaine fois installe via le gestionnaire de paquet. Ca t'installera le prog dans /bin (je crois) et le rendra accessible depuis n'importe quel dossier, et aussi t'installera le manuel sur ton pc.

Ok merci pour ton aide !
cela fonctionne

dernière petite question :
Puis-je créer un raccourcis pour éviter de lancer le terminal, et faire./eclipse ?