Should AdvancedSourceLookupDirector look to JavaSourceLookupParticipant before AdvancedSourceLookupParticipant?

[stephendnicholas]

Hi,

I'm experiencing an issue with Ctrl + I inspecting in debug mode, which I think could be a bug, but I wanted to check first and see if anyone has any advice.

I've also raised a discussion thread in the m2e project, as it is related: eclipse-m2e/m2e-core#1713

The setup:

• A maven project in Eclipse
• This has some dependencies, but not the class I'm attempting to inspect
• The project itself makes use of org.eclipse.jetty code to start-up a server and has the class I'm attempting to inspect on the "extra classpath"
• I have a custom Eclipse plugin that programmatically creates an ILaunchConfiguration, and uses this to launch the maven project
• On this ILaunchConfiguration, I have specified a custom source path, which include an entry for the class I'm attempting to inspect

The symptom I'm seeing is that when I try to inspect the code, with Eclipse's Advanced Source Lookup enabled, I get an error dialog that states:

Unable to evaluate the selected expression:
To perform an evaluation, an expression must be compiled in the context of a Java project's build path. The current execution context is not associated with a Java project in the workspace.

Whereas with Advanced Source Lookup disabled, it works fine.

I've included some information on the m2e discussion about the flow that the code looks to take, but I think the crux of the matter is a question of whether AdvancedSourceLookupDirector should look to the JavaSourceLookupParticipant before the AdvancedSourceLookupParticipant?

Currently it looks to AdvancedSourceLookupParticipant, but I think if it were to look to JavaSourceLookupParticipant first then the IJavaLaunchConfigurationConstants.ATTR_SOURCE_PATH on the ILaunchConfiguration would be referred to in preference, prior to any of the advanced lookup containers or resolvers.

Hope that makes sense, and please feel free to ask any clarifying questions

Thanks,

Steve

Note:

• I believe the above is also possibly related to the issues:
  • Issue with JAR in debug mode with m2e ("no java context") #86
  • Regression: Expressions broken for Remote Java Application in recent Eclipse versions #398