Eclipse+tomcat+maven Debug always occurs when source not Found/edit lookup path ... Solution to the problem

Eclipse+tomcat+maven Debug always occurs when source not Found/edit lookup path ... Solution to the problem

This problem has been tangled for a long time ....

The environment in which the problem arises

Ied:eclipse

Package Management: Maven

Container: Tomcat

Source code in the project debug struts

Problem description

After writing the code, think about tracking the source to see, but always appear

Follow the previous experience and click [Edit ...] directly. Associated with this project, you can debug. After the association is completed, the following conditions occur

Suddenly appear the breakpoint point to the source code, and then disappear, continue to appear above the situation.

Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... Baidu ..... google .... (It 's hard to take him as a dividing line )

Solution Solutions

An eclipse plugin called Sourcelookup has been added to MAVEN development tools, installed in Eclipse install new software.
Address is
http://ifedorenko.github.com/m2e-extras/

However, there is a problem with installing MAVEN development tools before you have to install M2E, and it is necessary to 1.6+ (may change when I install) and get the address of various versions of M2E from the URL below
Http://www.eclipse.org/m2e/m2e-downloads.html

Restart eclipse after full installation, I have a suncertpathbuilderexception error when I install Maven

View:
http://www.69900.com.cn/a_small_mouse/article/details/50291045

This is a perfect solution to this problem ^_^. Can only say too TM tired, but very easy ~ ~

Eclipse+tomcat+maven Debug always occurs when source not Found/edit lookup path ... Solution to the problem