Eclipse FAQs Solutions

1, MAVEN project, start error classnotfoundexception, because of Tomcat under the \web-inf\classes directory, Java files are not compiled into a class file. Workaround:

In the \web-inf\classes directory, add the folder directory that you want to compile.

Second, Eclipse has been reported an internal error occurred during: "Building Workspace". GC Overhead limit exceeded

The project that was recently imported into eclipse is very large, and every time eclipse starts, it returns to update workspace and then keeps saying:

An internal error occurred during: "Building Workspace". GC Overhead limit exceeded

This error.

Workaround:

The reason is that the eclipse default configuration memory is too small to change the Eclipse.ini file under the Eclipse installation folder.

Eclipse.ini default files are as follows:

Modify the following:

-xms512m-xmx1024m

The first is the smallest initialization memory and the second one is the largest occupied memory

You can also add-xx:maxpermsize=1024m, which means that you always have the maximum memory when compiling a file, restarting eclipse

If your computer's memory is large enough, allocate a little more eclipse. I will be set to 512m or error, simply set to 1024.

-xms512m-xmx1024m-xx:maxnewsize=-xx:maxpermsize=1024m

Third, Eclipse Building workspace too slow or JS error problem solved

1.js File Error Resolution

Right-click Project->properties->builders (Note: JavaScript validator also causes build workspace to be too slow)

2.Eclipse has been constantly building workspace perfect solution summary (from: http://blog.163.com/shadow_wolf/blog/static/18346909720145279519222/)

(1), Solution
Method 1: Modify the Eclipse startup file Eclipse.ini to add a startup parameter parameter to the-VMARGS-XMX512M
Method 2. Turn off the auto-build workspace: Project--Build auto ....
Method 3 Adds a command to the Eclipse.ini style-clean

(2), increase the maximum amount of memory available for eclipse operation
What to do: Modify the Eclipse.ini in the Eclipse directory,-xmx512m, such as change to-xmx768m

(3), reduce the plug-in that automatically starts after Eclipse starts
Specific operation: in Preferences, general, startup and Shutdown: Remove the items except the Plug-ins activated on startup (such as Mylyn, etc.) and remove them.
Effect: After you start eclipse, there will be a initialing Java tools scroll bar that will find a lot faster.

(4), reduce the compilation needs to verify the project, improve the compilation speed
Specific operation: In Preferences, validataion will be irrelevant validator removed, such as: I will not have nothing to do with me JPA, JSP, WS are removed.
Effect: When compiling a project, Eclipse runs a few validator projects, and it's really fast.

(5), turn off automatic compilation
What to do: Project--Build automatically
Effect: Automatic compilation does not start after code modification is saved.

(6), in clean, you should pay attention to the options
What to do: Project, clean
Note: At the bottom are: build the entire workspace and build only the selected Projects
To check according to your own situation, because the default option is to compile the entire workspace.

(7), display memory usage (can be manually gc)
How to do: Preference, General and Show Heep status

(8), save your own perspective
Specific operation: 1. Window, Save perspective as
2. Preference, perspective, make default sets the perspective you have just created or your own common

(9), close the automatic release of the server

Action: Never publish automatically, publishing, Server

In development, it was found that Eclipse's Build Workspace was slow and slow, as long as it was caused by validating the static files such as JS, CSS, XML, and so on.

I encountered the problem is that the project has a JS file is very large, how can not build the past, has been build, you can not do other work, change a file

Still have to wait until build workspace finished to save, feel very depressed, groped for a half day finally fix ....

1. The first is here window--> Preferences-Validation

Get rid of this column of build here ....

2. Right-click on your project-->properties this option

Find the Include Path option under JavaScript, see the Source tab on the right, excluded this, which means the build workspace does not contain the content

Double-click the Excluded Entry option, click the Add button to add the folder you want to ignore

Click Finish and you're done.

Click OK, you can try the clean project and you will find a lot faster. These scripts are no longer validated when Eclpse is turned on.

Eclipse FAQs Solutions