Download and unzip
Eclipse is an open source IDE. You can download Eclipse for free. Please make sure you are downloading a version >= 3.5 (Java EE version including web tools including a XML and XSLT editor.
Then unzip Eclipse into a local folder.
During the first start of Eclipse you will be asked to name a folder for the workspace. It might make sense to create and use an own folder outside the Eclipse folder. This is useful in order to protect the workspace while reinstalling newer version of Eclipse later on. The Eclipse workspace is also the standard location of projects that are checked out from CVS.
the workspace folder should be also a local folder to achieve reasonable performance.
Default compiler from Eclipse
In order to use the Eclipse compiler instead of the Java standard compiler you have to configure some settings. Select Menu Windows->Preferences and set your Global Entries like shown below:
The jdtCompilerAdapter.jar is normally part of the org.eclipse.jdt.core_x.x.x.jar file, so you should extract it with any unzip utility
If you will get an OutOfMemoryError in the compile run you need to choose Run->External Tools -> External Tools click the 'JRE' tab in your ANT and choose 'Separate JRE'. Within the VM arguments please enter '-XmX256m' to configure the memory used by the compiler.
While working with eclipse
If you get an OutOfMemoryError while working with in Eclipse you should try to change your startup parameter
- Windows: add start parameter to your Exlipse shortcut e.g. 'eclipse.exe -vmargs -Xmx512m'
- Mac OSX: open Finder, go to Eclipse, show package content, open Eclipse.ini, add memory settings
openFile -vmargs -XX:MaxPermSize=1024m -Xms256m -Xmx2048m
Heap Memory is the storage for Java objects
It is the runtime data area from which memory for all class instances and arrays are allocated. It is created at the JVM start-up.
- -Xms = initial java heap size
- -Xmx = maximum java heap size
Heap size does not determine the amount of memory your process uses. If you monitor your java process with an OS tool like taskmanager, you may see the amount of memory you use exceed the amount you have specified for -Xmx. -Xmx limits the java heap size, java will allocate memory for other things, including a stack for each thread. It is not unusual for the total memory consumption of the VM to exceed the value of -Xmx.
Non-Heap Memory is used by Java to store loaded classes and other meta-data
It is created at the JVM startup and stores per-class structures such as runtime constant pool, field and method data, and the code for methods and constructors, as well as interned Strings.
- -XX:MaxPermSize=1024m = maximum Non-Heap memory
Stack Memory is the amount of memory each thread is given
Xss determines the size of the stack. If the stack space is too small, you will see an exception like java.lang.StackOverflowError.
- -Xss1024k = size of the stack
Keep the path of your Eclipse Workspace short (e.g. C:\eclipse\ws). Because Windows file names are limited to 256 character and your generated function names including all directories could get on that limit.
- http://www.eclipseproject.de/ (German)