You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During remote debugging a Maven project, if stepping into a method of a workspace dependencies, the source lookup fails. I found that adding the following line to the launch configuration solves the issue: <stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER" value="org.eclipse.m2e.launchconfig.sourcepathProvider"/>
During remote debugging a Maven project, if stepping into a method of a workspace dependencies, the source lookup fails. I found that adding the following line to the launch configuration solves the issue:
<stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER" value="org.eclipse.m2e.launchconfig.sourcepathProvider"/>
I'm not sure if this causes any unwanted side effects but adding
org.eclipse.jdt.launching.remoteJavaApplication
to thesupportedTypes
set could be a possible way to get this working.While investigating this I found another issue:
The method
MavenLaunchConfigurationListener.updateLaunchConfiguration
should also callMavenRuntimeClasspathProvider.disable
if the launch configuration's project is not a Maven project anymore.The text was updated successfully, but these errors were encountered: