Source problem of Engineering dependent debugging in Eclipse Maven workspace (GO)

When using MAVEN development, because the project is usually divided into several modules (the main module depends on other modules), the debugging process need to see the other module code is a long-seeing requirement.

This article describes how to set up to meet this requirement when you debug:

(i) Runtime selection dependent workspace Resolve Workspace artifacts

(ii) Refresh options Check Refresh resources upon completion

(iii) Source tab added to workspace workspace

If you need to see the source of the third-party jar package that Maven relies on when debugging, you need to set the M2eclipse Plugin, window > Preferences > Maven, and tick the download Artifact Sources on the right.

Source problem of Engineering dependent debugging in Eclipse Maven workspace (GO)