Eclipse.ini parameter settings (Maven integration for Eclipse JDK Warning)

After installing the Eclipsemaven plugin, the Eclipse startup issue: Maven integration for Eclipse JDK Warning.
Workaround: 1. To set up a native-installed JDK folder for the JRE used by Eclipse: 1.1 Add two lines to Eclipse.ini

-vm

C:\Program Files\java\jdk1.6.0_10\bin\javaw.exe

Note: To write in two lines, write on one line does not take effect, the two lines to be set before-vmargs, otherwise it will not take effect.

1.2 or set eclipse--windows--preferences--java--installed JREs to change the JRE home to the JDK folder.

The experiment found that step 1.2 can not be done, but it is recommended to configure the development environment is a step, and the first step of the two lines can also be written

-vm

C:\Program files\java\jdk1.6.0_10\bin\

Test hair now CentOS 6.3 x86_64, if designated as/usr/custom/jdk1.6.0_37/bin/java.exe will be prompted to find the JDK,

Can only be configured as:/usr/custom/jdk1.6.0_37/bin/

2. Configure the Eclipse.ini file: first explain the file-vmargs the meaning of the common parameters:
-vmargs
-xms40m
-xmx256m
-xx:permsize=64m
-xx:maxpermsize=128m-vmargs: Description is followed by the VM's number of references
-xms40m: Virtual machine occupies the minimum memory of the system, initial allocation
-xmx256m: Virtual machine occupies the maximum memory of the system, on demand
-xx:permsize: Minimum heap size.

Generally reported insufficient memory, are said that this is too small, the remaining heap space is less than 5% will be warned, it is recommended to set this slightly
A little bigger, just set it up by the size of your machine's memory. But not more than MaxPermSize.

-xx:maxpermsize: Maximum heap size.

This is also more appropriate, so if it fails. First, adjust the-xms40m: set it smaller,

will be able to solve this problem. PermSize and MaxPermSize refer to the virtual machine's limitations of allocating memory for these reflective objects such as the Java permanently generated object (permanate generation). The memory is not included in the heap memory area.

3. Solve the failed to creat Java Virtual machine problem:

Open the Eclipse.ini file under the Eclipse installation folder and change:

--launcher. Xxmaxpermsize

128M;

For:

--launcher. Xxmaxpermsize
256m

Can be tested: http://blog.csdn.net/yuanfei_1988/archive/2010/10/02/5919168.aspx

4. STS-2.9.1 's Eclipse.ini configuration

-vm
C:/java/jdk1.6.0_30/bin/javaw.exe
-startup
Plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502
-product
Com.springsource.sts.ide
--launcher.defaultaction
OpenFile
--launcher. Xxmaxpermsize
384M

-vm
/usr/zskx/java/bin/java
-vmargs
-dcom.sun.management.jmxremote
-dosgi.requiredjavaversion=1.5
-xverify:none
-xmn128m
-xms256m
-xmx768m
-xss1m
-xx:permsize=128m
-xx:maxpermsize=512m

-xx:+useparallelgc
-xx:+disableexplicitgc
-xnoclassgc
-xx:+useparnewgc
-xx:+useconcmarksweepgc
-xx:cmsinitiatingoccupancyfraction=85

Eclipse.ini parameter settings (Maven integration for Eclipse JDK Warning)