[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [che-dev] che-dev Digest, Vol 38, Issue 6
|
>> As i understand we talk about server-side code, right?
>> Check that you set breakpoints NOT to the GWT components
Correct; I was wanting to debug server-side plugins with Visual Studio Code. Not GWT.
>> I have been using Chrome's built-in debugger with the gwt superdevmode and
>> it sends the source maps to Chrome well. I have not tried using VSCode to
>> do the debugging yet.
Thanks! Great tip for debugging GWT! Appreciated!
>> 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 :-)
I’ll look again and file one, if I can’t see an Issue. I’m up and running with Eclipse, so that’s good for what I need now.
Thank you all for your support! Wonderful!
Andrew
> On 7 Feb 2018, at 16:59, che-dev-request@xxxxxxxxxxx wrote:
>
> Send che-dev mailing list submissions to
> che-dev@xxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://dev.eclipse.org/mailman/listinfo/che-dev
> or, via email, send a message with subject or body 'help' to
> che-dev-request@xxxxxxxxxxx
>
> You can reach the person managing the list at
> che-dev-owner@xxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of che-dev digest..."
>
>
> Today's Topics:
>
> 1. Debugging Che plugins and source unknown (Andrew McLachlan)
> 2. Re: Debugging Che plugins and source unknown (Jonah Graham)
> 3. Re: Debugging Che plugins and source unknown (Andrew McLachlan)
> 4. Re: Debugging Che plugins and source unknown (Vitalii Parfonov)
> 5. Re: Debugging Che plugins and source unknown (Jonah Graham)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 07 Feb 2018 14:35:46 +0000
> From: Andrew McLachlan <andrew.mclachlan@xxxxxx>
> To: che developer discussions <che-dev@xxxxxxxxxxx>
> Subject: [che-dev] Debugging Che plugins and source unknown
> Message-ID: <0B2F87AE-6F10-4A2C-B73C-A5D2CF9F8870@xxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://dev.eclipse.org/mailman/private/che-dev/attachments/20180207/10a1ce5f/attachment.html>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 7 Feb 2018 14:45:54 +0000
> From: Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
> To: che developer discussions <che-dev@xxxxxxxxxxx>
> Subject: Re: [che-dev] Debugging Che plugins and source unknown
> Message-ID:
> <CAPmGMvgXGmL-ZxgTLCReUxn9CdY9gVnv_NQuTwojwTesZTXLiQ@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> I have been using Chrome's built-in debugger with the gwt superdevmode and
> it sends the source maps to Chrome well. I have not tried using VSCode to
> do the debugging yet.
>
> ~~~
> Jonah Graham
> Kichwa Coders Ltd.
> www.kichwacoders.com
>
> On 7 February 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
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://dev.eclipse.org/mailman/private/che-dev/attachments/20180207/b62911e8/attachment.html>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 07 Feb 2018 14:53:27 +0000
> From: Andrew McLachlan <andrew.mclachlan@xxxxxx>
> To: che developer discussions <che-dev@xxxxxxxxxxx>
> Subject: Re: [che-dev] Debugging Che plugins and source unknown
> Message-ID: <8E07EEA9-8DD6-489B-910B-F2D944398884@xxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
>
> 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
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://dev.eclipse.org/mailman/private/che-dev/attachments/20180207/56dcaed9/attachment.html>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 7 Feb 2018 17:06:35 +0200
> From: Vitalii Parfonov <vparfono@xxxxxxxxxx>
> To: che developer discussions <che-dev@xxxxxxxxxxx>
> Subject: Re: [che-dev] Debugging Che plugins and source unknown
> Message-ID:
> <CAH2TVYXqizng15Qo2jsPowkv3MoUwtA5VY6uRB2jAaHdiZTVsg@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://dev.eclipse.org/mailman/private/che-dev/attachments/20180207/e958830a/attachment.html>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 7 Feb 2018 16:58:51 +0000
> From: Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
> To: che developer discussions <che-dev@xxxxxxxxxxx>
> Subject: Re: [che-dev] Debugging Che plugins and source unknown
> Message-ID:
> <CAPmGMvhPyWZ7JSAEOC4EQSixbE98aVj94eseiadbJ62CzasPgw@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> 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
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://dev.eclipse.org/mailman/private/che-dev/attachments/20180207/aa6570ba/attachment.html>
>
> ------------------------------
>
> _______________________________________________
> 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
>
>
> End of che-dev Digest, Vol 38, Issue 6
> **************************************
