Eclipse cannot associate source code with MAVEN Tomcat plug-in deployment

First, install the Sourcelookup plugin:

Second, add source in source lookup path:

2.1) Add the source code of the project or the whole work space (not even your own codes can not be viewed, default is not added)

2.2) Add the source of the jar package that Maven dependency imported (with Maven plugin only)

2.3) Open Source lookup path There are three ways:

Third, restart the debugger (not eclipse)

First, install the Sourcelookup plugin:

Update site:

1) http://bjmi.github.io/update-site/(3.8.2 available, follow-up description of pin pieces to this plug)

2) http://ifedorenko.github.io/m2e-extras/(the plugin is not available)

Second, add source in source lookup path:

2.1) Add the source code of the project or the whole work space (not even your own codes can not be viewed, default is not added)

2.2) Add the source of the jar package that Maven dependency imported (with Maven plugin only)

2.3) Open Source lookup path There are three ways:

1) in Debug configurations

Select the Maven build on the left, or create a new MAVEN build

Enter name, select workspace, enter goals, and then select Source tab on the right

Click Add to add the source lookup path; Add the source code of the project or the whole work space (not even your own codes can not be viewed, default is not added)

Added source for Maven dependency imported jar package (only with Maven plugin)

2.2) In Debug view, right-click on the thread that is running, select Edit Source Lookup ...;

2.3) Click the source not Found button in the Open Class File window of the breakpoint thread management.

Third, restart the debugger (not eclipse)

Also, if you do not use MAVEN to start the service, there may not be a problem with this issue, such as starting the service with the following two jetty plug-ins:

Update site:

1) http://eclipse-jetty.github.io/update/

2) http://run-jetty-run.googlecode.com/svn/trunk/updatesite/

Eclipse cannot associate source code with MAVEN Tomcat plug-in deployment