Eclipse installation configuration Summary

Preface
Eclipse is the most popular and powerful Java ide with a wide range of plug-ins. It can be used as development tools such as J2EE, C, C ++, And. net. Plug-ins must be installed to support web development and other application development. This is an advantage of eclipse and a disadvantage of eclipse. The advantage is flexibility and the disadvantage lies in the trouble. This section describes how to install and configure the plug-in eclipse in windows, how to optimize it, and how to solve common problems, and how to use eclipse as a plug-in solution for J2EE development tools. Note that eclipse is an IDE tool developed by Java and must support the Java Runtime Environment. The latest eclipse3.2.2 requires JDK of version 1.4 or later.

1. Download and install eclipse
Open www.eclipse.org website;
Decompress eclipse-sdk-3.2.1-win32.zip to a directory. If you decompress the package to F: \, an F: \ folder is generated, and all the files and folders under the Plugins directory are copied to F: \ eclipse \ plugins: Copy all the files and folders in the features directory to F: \ eclipse \ features;
Run f: \ eclipse \ eclipse.exe to start a Chinese version of Eclipse.

Complete. The language package nlpack1-eclipse-sdk-3.2.1-win32.zip is actually an Eclipse plug-in!
Eclipse plug-ins actually have a directory specification for Eclipse, eclipse \ features, eclipse \ plugins, which is also very simple during installation. The method described above is one of them, here I call it the "intrusive plugin installation method ". From the above plug-in installation process, we can see that the "intrusive plugin installation method" is to simply copy eclipse \ features and eclipse \ plugins in the plug-in to eclipse \ features and eclipse \ plugins In the eclipse installation directory. you can, this installation method has a serious defect, that is, it cannot be uninstalled after installation, and the installation process is irreversible. It is impossible to flexibly configure and manage the installed plug-ins.

2. Non-Intrusive plug-in Installation Method (links installation method)
Since there is an intrusive installation, there is also a "non-intrusive installation", and someone has become the links installation method. The following describes how to install it :).
Non-Intrusive installation can also be divided into two types: absolute path installation method and relative path installation method. First, check the installation method of the absolute path.

In the ghost installation process, We decompress the Chinese language package nlpack1-eclipse-sdk-3.2.1-win32.zip to a place where the directory structure of the F: \ myplugins directory folder is as follows:
NLpack1-eclipse-SDK-3.2.1-win32
Eclipse
Features
Plugins
Paths with the following content: Path = F:/myplugins/NLpack1-eclipse-SDK-3.2.1-win32 with the path delimiter "/" or "\". In this way, the plug-in is installed.

The above is the "non-intrusive absolute path plug-in installation" method. The following describes how to change the absolute path to relative so that eclipse does not depend on the absolute path. This is the advantage of relative path installation.

During installation in the absolute path, we create a new links and myplugins folder under the installation directory F: \ eclipse, and decompress the Chinese language package nlpack1-eclipse-sdk-3.2.1-win32.zip to F: \ eclipse \ myplugins. The directory structure remains unchanged. Then in the linksdirectory to modify a new file nlpack1-eclipse-sdk-3.2.1-win32.txt, the content is as follows: Path = myplugins/NLpack1-eclipse-SDK-3.2.1-win32, so you can.

Note that the plug-in directory myplugins must be built under the eclipse installation directory and can be named at will. It is best to put all plug-ins in this directory (for ease of management ), each plug-in corresponds to a text configuration file in the links directory. The links directory name can only be links.

This installation process is very clear, so I will not summarize the installation process. In addition, some plug-ins are installed online, which is a different matter. However, I strongly recommend you use the links installation method.

Iii. Extended ipve to J2EE ide
Eclipse is a Java ide. to be used as a J2EE development tool, you need to install plug-ins. There are also many plug-ins. To save your precious time, I will introduce the best use of these plug-ins, WTP, the most popular and easy-to-obtain plug-in, is an open-source plug-in with a broad user base and developers. The emergence of WTP is to rewrite the development history of Java ide. More accurately, WTP started to get angry at the beginning! Now it's just a little more than a year.
The following describes how to obtain and install the configuration. Open the downloads column at www.eclipse.org. There is a ranking on the page that shows the download of hotspot plug-ins. WTP is always ranked at No1. The difference between the two is that the SDK has the source code. Nothing else! Running without source code is a little faster (theoretically), but I don't feel it, huh, huh. There are many download addresses, so I will not talk about the weak issue, and then install it according to the method described above.

If you are doing J2EE or Java Web development, then you directly download a WTP: wtp-all-in-one-sdk-R-1.5.3-win32.zip integrated with Eclipse, it will be better, you need to install at most two language packs, this saves time.

Iv. Optimization

The purpose of optimization is to make eclipse run more stable, smoother, and faster!
First: Memory Optimization
After eclipse is installed, there is a config. ini file in the installation directory. The content is as follows:
-Vmargs
-Xms40m
-Xmx256m
This file is used to configure the memory allocation scheme during eclipse startup. XMS indicates the initial memory size and xmx indicates the maximum available memory size. The default configuration is the configuration that minimizes eclipse resource consumption. If your project is relatively large, this configuration must be changed. Generally, it can be adjusted to 128,384. If the project is larger, the configuration will be larger, depending on the actual situation. The size of this parameter configuration is critical. If it is too small, the garbage collection in eclipse will be too frequent, resulting in a slow process or crash due to memory stack overflow. If it is too large, eclipse will eat a lot of memory, and the garbage collection cycle will become longer, but each collection will be slow, affecting usage. So you need to weigh the configuration and try it!
Second, plug-in Optimization
When you install multiple plug-ins, it will consume a lot of memory resources. Therefore, you only need to Remove unused plug-in configuration files from the links directory. Note that it is not deleted, you can create a new _ useless in the links directory, move unused configuration files to it, and then move them back when they are used.

5. FAQs

1. The eclipse Language Pack or other plug-ins are not installed
Original cause: You may have run the English version of eclipse before installing the Language Pack.
Solution: delete all files and folders except config. ini in configuration to ensure that the plug-in installation and configuration are correct.

2. Eclipse cannot be started
Original cause: JDK is not correctly installed or JDK is not configured. It is usually required after JDK is installed, however, if you have installed JDK multiple times or use the JDK that has been downloaded from the previous system, you need to configure JDK and pay attention to the requirements of eclipse for the JDK version.
Solution: Configure JDK. That is, configure the system variables java_home, classpath, and path, and reinstall JDK if necessary. If the problem persists, it may be that your eclipse file is damaged or lost, or your hard disk has a bad track. What should I do.

3. You want to reconfigure the workspace.
Original cause: You have a workspace by default, which is depressing.
Solution: delete all files and folders except config. ini in configuration to ensure that the plug-in installation and configuration are correct.

4. Unable to compile and Package
Original cause: excluding the above problems, it should be that the packages on which your program depends cannot be found.
Solution: add the required package in the build path. # Java Column