工欲善其事, its prerequisite-ecplise configuration and optimization

Encoding settings under 1.eclipse: When using templates to create new jsp,xhtml files in Eclipse, the default encoding is: Iso-8859-1. ISO-8859-1 encoding for Chinese display is not supported, if you want to support Simplified Chinese, the encoding should be GBK or GB2312 or UTF-8 (recommended). Right-click the menu bar window--> Preferences--> Enter the JSP in type filter text; --> Select the following JSP-> Select the encoding in creating files group to UTF-8 code if you want to make the new project, Java files directly to the UTF-8 to make the following work: 1, windows-> Preferences ... Open the Preferences dialog box, the left navigation tree, navigate to General->workspace, right text file encoding, select Other, change to UTF-8, and later create a new project. Text file in its Properties dialog box Encoding is the UTF-8. 2, Windows->preferences ... Open the Preferences dialog box, left navigation tree, navigate to general->content Types, right context Types tree, point Open Text, select Java Source File, and in the following default Encoding enter UTF-8 in the input box, click Update, then set the Java file encoding to UTF-8. Other Java application development related files such as properties, XML, etc. have been specified by the Eclipse default, respectively, Iso8859-1,utf-8, such as in the development of the need to change the encoding format can be specified here. 3, after the above two steps, the new Java file is UTF-8 encoding, Eclipse compile, run, Debug is no problem, but do RCP application of the product output, or plug-in output, it is always error, or can not compile the pass (the output to be compile), Or the output of the plug-in run when the Chinese display garbled. At this point need to RCP application, or plug-in plugin engineering build.properties Add a line, javacdefaultencoding ... = UTF-8. UTF-8 encoding when the output is compiled to know the Java source file. This setting requires that all Java source files be UTF-8 encoded and, if not all, referenced in Eclipse Help (Plug-in development environment Guide > Reference > Feature and Plug-in build configuration), it is recommended that all Java source files be UTF-8 encoded.

2. Cancel the word spell check myeclipse menu Window--general--editors--text editors--spelling--the right of the Enable spell checking the hook to remove the line, That is, the spelling of the word is canceled.

3. Remove modules that do not need to be loaded open the configuration window by Windows-preferences, then select the General-startup and Shutdown on the left, which shows the module loaded at eclipse startup at the right. You can remove some modules according to your own actual situation. Windows–>perferences–>general–>startup and shutdown

Turn off the useless startup items:

WTP WebService UI Plug-in,equinox provisioning platform Update Automatic

One is the UI view and one is the automatic update. I got rid of it.

4. Canceling automatic validation of project profiles at startup by default, Eclipse automatically validates each project's profile when it starts, which is a time-consuming process that you can select in Preferences window myeclipse-validation, Then in the validator list on the right, only the Manual items are preserved. If you need to verify the time only need to select the file, and then right-click the Myeclipse-run validation on it.

Windows–>perferences–>myeclipse–>validation put all except the manual below the point off, build only stay classpath dependency Validator Manual authentication method: On the file to be validated, right-click –>myeclipse–>run validation

5, modify the Eclipse installation directory Eclipse.ini files, increase the JVM's non heap memory eclipse settings are as follows: Open the Eclipse Profile Eclipse.ini and change the-XMX (its value represents the maximum amount of memory that the JVM can use)- xms256m-xmx1024m

6. Edit tool Window > Perferences > General > Editors > File Associations > in file types when modifying Eclipse edit jsp,xhtml pages Select *.jsp > in associated editors the setting you want to use is default.

7. Set the font size in window->perferences->general->appearance->colors and Fonts->text font Click Change to modify 8. The same variable problem description is highlighted in eclipse:

Use shortcuts or other reasons in Eclipse and accidentally press the wrong button so that the highlight of the variable is gone.
1. Solution:
Choice: windows-> Preferences->java->editor->mark occurences
Select the top check box, and there are a lot of them below.
The local variables is the highlight of the variable.
2. There are also simpler ways to:
The online search is toggle Mark occurrences (Alt + Shift + 0) This button does not press the icon for the shape of the small yellow color pen in the toolbar.
3. Change the color:
Selection: windows-> Preferences->java->editor->mark occurences-> The first line has a "annotations" click to enter, show the list, find occurrence annotation Choose color on the right.

Comment Modification for 9.Eclipse ctrl+alt+j

Create a new XML file. Enter the content:

1 <?xml version= "1.0" encoding= "UTF-8" standalone= "no"? >/** 2 * <p>project:credo ' s base</p> 3 * <P&G T;description: </p> 4 * <p>copyright (c) ${year} lioncredo.all Rights reserved.</p> 5 * @author <a HR ef= "Zhaoqianjava@foxmail.com" >LionCredo</a> 6 */import on the OK.

10.Eclipse set the number of words per line to prevent line wrapping as shown in the figure

Web wrapping is set up in the main menu--web.

11. About the Eclipse Profile export issue: Eclipse's default configuration generally does not meet our requirements, we will generally modify some of the configuration, such as fonts, background color, shortcuts and some template and so on, so convenient for our development. But when we create a new workspace, Eclipse uses the default configuration, how to export our custom configuration and import new workspaces. Method One: Use Eclipse's export function (not recommended, many configurations cannot be exported)

Working directory to select Export->general->preference, so you can export the EPF file, the new workspace can import the profile with import, this method can indeed import most of the configuration, but not all, Many configurations will be lost after import.

method Two: Will workspace/.metadata/.plugins/ The. Settings folder in the Org.eclipse.core.runtime is copied out, with all the configuration files in it, and the. Settings folder in the new workspace is replaced with the. Settings folder in the newly created space. (Some netizens are replacing the. plugings folder, but the. plugings folder is too large to actually replace the. Settings folder,. Settings are only hundreds of K.) ）

Turn from: http://my.oschina.net/zhaoqian/blog/66545