Re: [che-dev] Debugging Che plugins and source unknown

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

I was referring to the GWT code when I said Chrome. I use Eclipse IDE for debugging the server code. From the sounds of it you need to file a bug against the Java Debug Adapter you are using requesting it implement more of the advanced source lookup features Eclipse has :-)

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

On 7 February 2018 at 15:06, Vitalii Parfonov <vparfono@xxxxxxxxxx> wrote:

As i understand we talk about server-side code, right?

Check that you set breakpoints NOT to the GWT components 

On Wed, Feb 7, 2018 at 4:53 PM, Andrew McLachlan <andrew.mclachlan@xxxxxx> wrote:

I should add that I can successfully use Eclipse Java EE and its source lookup so my question is specific to Visual Studio Code.

On 7 Feb 2018, at 14:35, Andrew McLachlan <andrew.mclachlan@xxxxxx> wrote:

Hi again,

I have a question about attaching to Che plugins running in the workspace.

I can attach to the plugins using Visual Studio Code, Java extensions and attaching to port 32813->4403.

I can set breakpoints in source file that I’ve added to Visual Studio Code and those breakpoints appear to be hit but I am unable to step through the source once the breakpoint appears to be hit. Visual Studio Code says Unknown Source.

Has anyone encountered an issue debugging in this way or there’s a better way to debug the Che plugins?

As always, thanks in advance for your great support!

Andrew

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev

--

Vitalii Parfonov

Che IDE Team Lead

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev