Re: [wtp-dev] Adherance of NodeJS debugger and JSDT document model

[Ilya Buziuk]

Hi, Angelo
really sorry that TypeScript patch is not yet reviewed :/
I think Victor is going to do it in the nearest future (this issue is in
our current sprint backlog)


On Thu, Mar 23, 2017 at 8:07 PM, Angelo zerr  wrote:

> Hi Mickael,
>
> > As I'm working on TextMate and Language Server, I have the impression
> that using TestMate grammars and a JavaScript language server such as the
> one embedded in VSCode can lead to very good results in term of JS edition.
>
> Totally agree with you! I have followed this idea with typescript.java by
> consuming tsserver and it works with Javascript only too. You can try
> typescript.java which provides a custom "Javascript (Salsa) Editor" which
> consumes TextMate and tsserver  and it works well: completion, hover,
> outline, hyperlink, validation, references, etc. ) Performance are very
> good. IMHO completion is more advanced than JSDT (Thank to TypeScript
> tsserver).
>
> > This combo could do most of the work, and the internal JSDT model would
> still be useful for advanced operations not covered by the VSCode Language
> Server for JS.
>
> I tell me which advanced operations, are you speaking?
>
> > However, I'm wondering how much the Node/JS debuggers in Eclipse IDE do
> rely on the JSDT internal model for JS files. Do they integrate with the
> AST/DOM, or do they remain at text level (so they could easily be used
> together with a totally different editor)?
>
> I can use the Node.js debugger with my custom TypeScript editor to debug
> TypeScript with SourceMap (by using a forked Node.js debugeur by waiting
> for the accept of the patch https://bugs.eclipse.org
> /bugs/show_bug.cgi?id=487465) which doesn't use JSDT AST.
>
> Regard's Angelo
>
> 2017-03-23 18:12 GMT+01:00 Mickael Istria :
>
>> Hi all,
>> As I'm working on TextMate and Language Server, I have the impression
>> that using TestMate grammars and a JavaScript language server such as the
>> one embedded in VSCode can lead to very good results in term of JS edition.
>> This combo could do most of the work, and the internal JSDT model would
>> still be useful for advanced operations not covered by the VSCode Language
>> Server for JS.
>> However, I'm wondering how much the Node/JS debuggers in Eclipse IDE do
>> rely on the JSDT internal model for JS files. Do they integrate with the
>> AST/DOM, or do they remain at text level (so they could easily be used
>> together with a totally different editor)?
>>
>> Thanks in advance for your insights!
>> --
>> Mickael Istria
>> Eclipse developer for Red Hat Developers 
>> My blog  - My Tweets
>> 
>>
>> ___
>> wtp-dev mailing list
>> wtp-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Adherance of NodeJS debugger and JSDT document model

[Ilya Buziuk]

Hi, Mickael
Great news about JavaScript LSP.
In terms of  debugger, I believe it does not rely on JSDT internal model at
all. Originally custom chromium editor[1] was used for debugging and we
implemented some tricks so that JSDT editor would be used by default while
debugging process.

[1]
https://github.com/ChromeDevTools/cdt-java/blob/master/plugins/org.chromium.debug.ui/src/org/chromium/debug/ui/editors/JsEditor.java#L15

On Thu, Mar 23, 2017 at 6:12 PM, Mickael Istria  wrote:

> Hi all,
> As I'm working on TextMate and Language Server, I have the impression that
> using TestMate grammars and a JavaScript language server such as the one
> embedded in VSCode can lead to very good results in term of JS edition.
> This combo could do most of the work, and the internal JSDT model would
> still be useful for advanced operations not covered by the VSCode Language
> Server for JS.
> However, I'm wondering how much the Node/JS debuggers in Eclipse IDE do
> rely on the JSDT internal model for JS files. Do they integrate with the
> AST/DOM, or do they remain at text level (so they could easily be used
> together with a totally different editor)?
>
> Thanks in advance for your insights!
> --
> Mickael Istria
> Eclipse developer for Red Hat Developers 
> My blog  - My Tweets
> 
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Status and future outlook of the JSDT debugger

[Ilya Buziuk]

Hi, Ivan
Does the SDBG support V8 remote debugger protocol [1] ? Chrome Remote
Debugger Protocol / WIP protocol is used for front-end debugging, but our
main Neon requirement was Node.js debugger (V8 protocol support is
required). Chromedevtools-Java tooling support both WIP & V8  so it was a
perfect match for us.

[1] https://github.com/v8/v8/wiki/Debugging%20Protocol


On Mon, Jan 23, 2017 at 4:20 PM, Ivan Markov  wrote:

>
>
>
>
>> On Sat, Jan 21, 2017 at 4:06 AM, Ivan Markov 
>> wrote:
>>
>> > Dear all,
>> >
>> > Being the maintainer of sdbg.github.io, the recent (2015-2016) rebirth
>> of
>> > the JSDT tooling is of course something I'm interested it.
>> > (... and unfortunately something I've slept through).
>> >
>> > Regarding the JSDT debugging story, as far as I understand there are two
>> > codebases in use:
>> > 1) The original JSDT Debug plugins, which support only Rhino
>> > 2) A fork of the old Chromedevtools-Java tooling from Google (last when
>> I
>> > looked at it - still in the Google Code times, it was a completely
>> > independent set of Eclipse plugins, is this still the case?)
>> >
>> > The following question to follow (obviously):
>> > Have you considered using the SDBG codebase, and if not, why not?
>> > Technical or legal issues?
>> >
>> >
>> No, we have not considered it. At least I have assumed it to be GWT only.
>>
>
> That's a pity, because the SDBG core is completely GWT agnostic. If you've
> seen the heading of the website, it says: "...and for JavaScript with
> Sourcemaps in general". I mean, GWT today is in no way different than any
> other -to-JavaScript transpiler, like TypeScript,
> CofeeScript, Scala.js etc. - it just takes a bunch of source files and
> produces JS output + sourcemaps.
>
> The GWT specifics - as much as there are any - are isolated in an
> additional optional plugin (com.github.sdbg.integration.jdt). As the
> plugin name hints, these are for the most part not even GWT - but Eclipse
> JDT specific: if you transpile from Java to JavaScript, SDBG can adopt the
> Eclipse JDT Java breakpoints and "pretend" that these are its own
> breakpoints, which is very valuable when you are working in an integrated
> J2EE+GWT environment and do not want to think whether you need a serverside
> = Java JDT, or a clientside = SDBG breakpoint.
>
> BTW, when I setup for forking the Dart Tools Eclipse debugging codebase
> (in 2013) to implement my own debugger, I did not do it lightly. Before
> that, I was fiddling with the classic (Rhino) JSDT debugger infrastructure
> and the Chromedevtools-Java codebase for a couple of months, but the
> results were not encouraging:
> - Already then Chromedevtools-Java was dead, with its sole maintainer no
> longer at Google. The JSDT debugger was also stagnating, I must say. As a
> comparison, Dart Tools was still very much alive and kicking at that time.
> - The Dart Tools debugger (also using the Chrome WIP protocol) had
> sourcemaps support built in. So I was able to get something up and running
> based off their codebase in less than a month.
> - Last but not least, both the JSDT debugger, as well as
> Chromedevtools-Java had implemented their own extra layer of abstraction on
> top of the core Eclipse debug (IValue, IDebugTarget, etc.) model. No
> offense, maybe they had their reasons to do so, but in practice, when I was
> prototyping sourcemaps support in JSDT and Chromedevtools-Java, these
> abstractions had the tendency to get in my way, rather than save me work.
>
> Anyway, just my 2c.
>
> Cheers,
> Ivan
>
>
>
>
>
>>
>> > Cheers,
>> > Ivan
>> >
>> >
>> >
>> >
>> > ___
>> > wtp-dev mailing list
>> > wtp-dev@eclipse.org
>> > To change your delivery options, retrieve your password, or unsubscribe
>> > from this list, visit
>> > https://dev.eclipse.org/mailman/listinfo/wtp-dev
>> >
>> -- next part --
>> An HTML attachment was scrubbed...
>> URL: > attachments/20170122/9cd406c3/attachment.html>
>>
>> --
>>
>> Message: 2
>> Date: Sun, 22 Jan 2017 11:04:39 -0500
>> From: Gorkem Ercan 
>> To: "General discussion of project-wide or architectural issues."
>> 
>> Subject: Re: [wtp-dev] Status and future outlook of the JSDT debugger
>> Message-ID:
>> > p...@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> On Sat, Jan 21, 2017 at 9:00 AM, Angelo zerr 
>> wrote:
>>
>> > Hi Ivan,
>> >
>> > I'm very glad that you post this question because in my case I need to
>> > debug TypeScript (in other mean debugging with source map).
>> >
>> > So I have created a patch for JSDT Chrome debugger at
>> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=487465 and sourcemap code
>> > is based on your sdbg work. See my 

Re: [wtp-dev] Silent failure in Neon javascript project, can't read javascript some javascript files

[Ilya Buziuk]

Hi, Adam
Outline issue should be is fixed in Neon.1 release (September 26), for now
you can try developer build[1]. I installed d3.js and it's minified version
and got full outline for it.

[1]
http://build.eclipse.org/webtools/committers/wtp-R3.8.1-M/20160912100321/R-3.8.1-20160912100321/

On Tue, Sep 20, 2016 at 12:36 PM, Adam Hardy 
wrote:

> I'm using Neon 4.6.0 and JSDT 1.0.0.v201605232053 and I set up a
> Javascript project.
>
> I included my own code as a Javascript resource at src/main/javascript,
> plus d3.min.js - which is not parsed by Eclipse, so I don't get an outline.
>
> I get a error in the console from Tern which says it's too big.
>
> Is there a limitation?
>
> Is there an alternative to Tern, which I only installed because of
> supposed ECMAscript 6 compatibility.
>
> Thanks
> Adam
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Clarify when JSDT completion is supposed to work

[Ilya Buziuk]

There are a few bugzillas which refer to broken CA for certain cases:

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=488912
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=497903

On Mon, Sep 12, 2016 at 11:36 AM, Mickael Istria  wrote:

> Hi all,
>
> As I'm testing the Neon.1 RC3 JavaScript package, I tried a few more
> scenarios than the usual (too) basic ones I'm doing. I got confused about
> JSDT's completion.
>
> In which cases is this supposed to work, in which cases not?
> I have found multiple places where we could expect some completion from
> JSDT and didn't manage to get anything. I didn't find a pattern that makes
> it return nothing. Can someone please clarify that? Is there a bugzilla
> already tracking such discussion?
>
> Thanks in advance.
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat 
> My blog  - My Tweets
> 
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] [URGENT] Two issues require PMC approval for RC4

[Ilya Buziuk]

Hello,
Tomorrow Eclipse RC4 is going to be released and there are two issues that
are utterly important to have in the Neon 1. Project leads of SSE and JSDT
have already approved those and for now PMC approvals are required. Please,
+1 those changes so that it would be possible to merge
Thanks in advance

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=500805
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=497856
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] JSDT issues need PMC approval for Neon.1 RC2

[Ilya Buziuk]

Thanks, everyone
all issues are now resolved and pushed to the master branch.
Getting ready to RC3  ;-)

On Wed, Aug 24, 2016 at 10:23 PM, Patrik Suzzi <psu...@gmail.com> wrote:

> Dear WTP developers,
>
> I have another JSDT bugfix that I want to candidate to enter RC2, and then
> Neon.1
>
> Bug 356606 - [formatter] Unwanted alignment on Enter when inside array
> literal
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=356606
>
> This is an annoying bug, that has been around since a long time.
> I read the https://wiki.eclipse.org/WTP_PMC_Defect_Review,
> I added a risk analysis as bug comment, and the Project Lead verified the
> fix and added the keyword "PMC" to the whiteboard.
>
> Hope this is good enough to be reviewed.
>
> *Best Regards,*
>
> *Patrik Suzzi*
>
> *Software Engineer, EclipsePlatform UI Committer*
> https://about.me/psuzzi
>
>
>
> On Wed, Aug 24, 2016 at 9:30 PM, Ilya Buziuk <ibuz...@redhat.com> wrote:
> > Thanks for approvals, Chuck
> > I just mixed everything up (gerrit approvals & PMC votes). So, in order
> to
> > have some changes in after RC1 the issue should have the following
> number of
> > PMC votes:
> >
> >> RC2 -> 1 PMC vote
> >> RC3 -> 2 PMC votes
> >> RC4 -> 3 PMC votes
> >
> >
> >
> >
> > On Wed, Aug 24, 2016 at 8:37 PM, Chuck Bridgham <cbrid...@us.ibm.com>
> wrote:
> >>
> >> Hi Ilya,
> >>
> >> I was confused yesterday, and was thinking you needed Gerrit reviews...
>
> >>
> >> You are correct that 1 PMC vote is needed after RC1...
> >>
> >> add the questions outlined here:
> >> https://wiki.eclipse.org/WTP_PMC_Defect_Review
> >> and we'll get them approved...
> >>
> >>
> >> Thanks - Chuck
> >>
> >> IBM Tools development, Eclipse WTP PMC
> >> IBM Software Lab - Research Triangle Park, NC
> >>
> >>
> >>
> >> From:Ilya Buziuk <ibuz...@redhat.com>
> >> To:wtp-dev <wtp-dev@eclipse.org>, Chuck
> >> Bridgham/Raleigh/IBM@IBMUS, Victor Rubezhny <vrubez...@redhat.com>
> >> Date:08/24/2016 01:32 PM
> >> Subject:[wtp-dev] JSDT issues need PMC approval for Neon.1 RC2
> >> Sent by:wtp-dev-boun...@eclipse.org
> >> 
> >>
> >>
> >>
> >> Hello, guys
> >> Tomorrow is Neon.1 RC2 and there are three JSDT issues that need PMC
> >> approval. Chuck said that he would be able to +1 those, but we still
> need
> >> another one to merge. Basically, Victor is in the middle of his
> relocation
> >> and might be unavailable till the end of the week, so we need one more
> PMC
> >> approval. Please, +1 the change so that we will be able to officially
> have
> >> it in the upcoming release candidate.
> >> Thanks
> >>
> >> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=496348
> >> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=500138
> >> [3]
> >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497685
> ___
> >> wtp-dev mailing list
> >> wtp-dev@eclipse.org
> >> To change your delivery options, retrieve your password, or unsubscribe
> >> from this list, visit
> >> https://dev.eclipse.org/mailman/listinfo/wtp-dev
> >>
> >>
> >>
> >> ___
> >> wtp-dev mailing list
> >> wtp-dev@eclipse.org
> >> To change your delivery options, retrieve your password, or unsubscribe
> >> from this list, visit
> >> https://dev.eclipse.org/mailman/listinfo/wtp-dev
> >
> >
> >
> > ___
> > wtp-dev mailing list
> > wtp-dev@eclipse.org
> > To change your delivery options, retrieve your password, or unsubscribe
> from
> > this list, visit
> > https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] JSDT issues need PMC approval for Neon.1 RC2

[Ilya Buziuk]

Thanks for approvals, Chuck
I just mixed everything up (gerrit approvals & PMC votes). So, in order to
have some changes in after RC1 the issue should have the following number
of PMC votes:

RC2 -> 1 PMC vote
> RC3 -> 2 PMC votes
> RC4 -> 3 PMC votes




On Wed, Aug 24, 2016 at 8:37 PM, Chuck Bridgham <cbrid...@us.ibm.com> wrote:

> Hi Ilya,
>
> I was confused yesterday, and was thinking you needed Gerrit reviews...
>
> You are correct that 1 PMC vote is needed after RC1...
>
> add the questions outlined here:  https://wiki.eclipse.org/WTP_
> PMC_Defect_Review
> and we'll get them approved...
>
>
> Thanks - Chuck
>
> IBM Tools development, Eclipse WTP PMC
> IBM Software Lab - Research Triangle Park, NC
>
>
>
> From:Ilya Buziuk <ibuz...@redhat.com>
> To:wtp-dev <wtp-dev@eclipse.org>, Chuck Bridgham/Raleigh/IBM@IBMUS,
> Victor Rubezhny <vrubez...@redhat.com>
> Date:08/24/2016 01:32 PM
> Subject:[wtp-dev] JSDT issues need PMC approval for Neon.1 RC2
> Sent by:wtp-dev-boun...@eclipse.org
> --
>
>
>
> Hello, guys
> Tomorrow is Neon.1 RC2 and there are three JSDT issues that need PMC
> approval. Chuck said that he would be able to +1 those, but we still need
> another one to merge. Basically, Victor is in the middle of his relocation
> and might be unavailable till the end of the week, so we need one more PMC
> approval. Please, +1 the change so that we will be able to officially have
> it in the upcoming release candidate.
> Thanks
>
> [1] *https://bugs.eclipse.org/bugs/show_bug.cgi?id=496348*
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=496348>
> [2] *https://bugs.eclipse.org/bugs/show_bug.cgi?id=500138*
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=500138>
> [3] *https://bugs.eclipse.org/bugs/show_bug.cgi?id=497685*
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=497685>___
> 
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] JSDT issues need PMC approval for Neon.1 RC2

[Ilya Buziuk]

Hello, guys
Tomorrow is Neon.1 RC2 and there are three JSDT issues that need PMC
approval. Chuck said that he would be able to +1 those, but we still need
another one to merge. Basically, Victor is in the middle of his relocation
and might be unavailable till the end of the week, so we need one more PMC
approval. Please, +1 the change so that we will be able to officially have
it in the upcoming release candidate.
Thanks

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=496348
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=500138
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=497685
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] breakpoints related bugs

[Ilya Buziuk]

Hello, Dobrin
Yes, please open a bugzilla for var hovering.

On Thu, Jul 14, 2016 at 11:44 PM, Alexiev, Dobrin <dalex...@ti.com> wrote:

> Thank you!
>
> For contributions: I will be able to test the latest builds from
> https://hudson.eclipse.org/webtools/job/jsdt-snapshots/ws/site/target/site-3.6.0-SNAPSHOT.zip
> when specific fixes are available. I don’t think I have much knowledge of
> the JSEE plugins code to even try to make a suggestion.
>
>
>
> BTW,
>
> I just realized one feature is not there: While debugging, if I hover with
> my mouse over “myVar” part of the expression “myVar.myProp.mySubProp.abc”
> in my JS editor, I see a tooltip with its current value. But if I hover
> over the last segment “abc” of the same expression nothing happens. If I
> want to see its value, I have to move the mouse to “myVar” and when the
> tooltip opens up I have to click to expand, scroll to “myProp”, click to
> expand, scroll to “mySubProp”, expand, etc. until I see “abc”. Would be a
> real time saver when I hover over “abc” to see its value. Do you want me to
> file a Bugzilla entry for this?
>
>
>
> Thank you again for your support!!!
>
> Dobrin
>
>
>
> *From:* wtp-dev-boun...@eclipse.org [mailto:wtp-dev-boun...@eclipse.org] *On
> Behalf Of *Ilya Buziuk
> *Sent:* Thursday, July 14, 2016 4:50 PM
> *To:* General discussion of project-wide or architectural issues.
> *Subject:* Re: [wtp-dev] breakpoints related bugs
>
>
>
> Hello, Dobrin
>
> Thanks for reporting. I have added both to Neon 1 backlog. We would
> definitely try to fix them and meet September deadline
>
> Contributions of any kind are also most welcome ;)
>
>
>
>
>
> On Thu, Jul 14, 2016 at 10:06 PM, Alexiev, Dobrin <dalex...@ti.com> wrote:
>
> Hello,
>
> I am currently evaluating if we can start using JSEE Neon for our
> development.
>
> I am was very impressed with the JSEE team for fixing two issues on the
> same day.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497706
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497424
>
> I also filed two bugs related to breakpoints. I was wandering if there are
> any plans for fixing these for the September release.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497685
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497703
>
> Thank you.
>
> Dobrin
>
>
>
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] breakpoints related bugs

[Ilya Buziuk]

Hello, Dobrin
Thanks for reporting. I have added both to Neon 1 backlog. We would
definitely try to fix them and meet September deadline
Contributions of any kind are also most welcome ;)


On Thu, Jul 14, 2016 at 10:06 PM, Alexiev, Dobrin  wrote:

> Hello,
>
> I am currently evaluating if we can start using JSEE Neon for our
> development.
>
> I am was very impressed with the JSEE team for fixing two issues on the
> same day.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497706
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497424
>
> I also filed two bugs related to breakpoints. I was wandering if there are
> any plans for fixing these for the September release.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497685
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497703
>
> Thank you.
>
> Dobrin
>
>
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Set a breakpoint in a node modules

[Ilya Buziuk]

Hello, Dobrin

This functionality should work OOTB, however the attached project is unavailable

Symantec Mail Security replaced test.zip with this text message. The
> original text contained prohibited content and was deleted.


Could you share the project via public link (google drive /  dropbox /
bugzilla) ?

On Fri, Jul 8, 2016 at 8:40 PM, Alexiev, Dobrin  wrote:

> Hello,
>
> When I debug my node application and I add a breakpoint in a file inside a
> "node_modules" folder, the code executes but the breakpoint does not halt
> the program execution.
> Is this a supported feature? If not, is there workaround for this?
> I attached the projects for reference.
>
> Thanks
> Dobrin
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Bad experience with Neon and JavaScript

[Ilya Buziuk]

Hello, Arián
Thank you for feedback - this is smth. we are seeking for now.

Basically, JSDT is still in transitional state. A lot of thing were changed
due to old parser (EcmaScript 3 support) replacement and some stuff might
be broken here and there. What is more, we are going to change parser one
more time for Neon.1  and use Closure Compiler (better performance, linting
+ no need to use Nashorn JS engine).
I have created a bug for having new wizard for custom json file [1] (for
now one can only use bower init / npm init wizards for creating bower.json
& package.json). It would be really great if you could address other issues
you had with JSDT in eclipse bugzilla, so that we would try to tackle them
for Neon.1 release - September 2016

P.S. Contributions of any kind are most welcome

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=497494

On Thu, Jul 7, 2016 at 2:59 PM, Arián Fornaris Fernández <
boniati...@gmail.com> wrote:

> Hi guys,
>
> I see lot of buzz around a JavaScript update in Eclipse Neon but honestly,
> I don't see a real change :(
>
> - I installed Eclipse for JavaScript and Web Developers via Eclipse
> installer (was a nice experience)
>
> - I created a JavaScript project and the first thing I see is that it keep
> using JavaScript libraries that are not updated since 2010 (system.js) and
> 2013 (browserWindow.js). I did a search for "console" and "log" and it just
> does not exist.
>
> - I wrote this code:
> class Pepe {
>   function lola() {
>   }
> }
> When I save it, I got a nashorn error "Undefined cannot be casted to
> String". If I write the right syntax it works fine.
>
> - Ok, let's try with something simpler:
> var a = "";
> 
> It does not show any completions, just keywords, and an old "pepe"
> function I wrote before, it seems to be cached somewhere.
> Actually, I don't get any JavaScript global objects completions, like Math.
>
> - Well... in the previous JSDT completions worked much much better.
>
> - I saw somewhere there is a new JSON editor (but I did not find a wizard
> to create a JSON file). I had to create it via New File wizard.
>
> In general, it was a frustrating experience :( I had lot of expectation
> for this release, but what I see are regressions or a work in progress.
>
> (I did not test the stuff around nodejs)
>
> Maybe I am missing something... some configuration... well, maybe it is
> just a matter of time, I know you are working hard on it and that there is
> a lot to do. I know there are other options like those based on tern.java
> (that works much better) but yet I prefer to keep on the standard tooling.
>
> Best regards,
> Arian
>
>
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Debugging Javascript - No source found

[Ilya Buziuk]

Thank you for reporting. I am going to provide a fix tomorrow

On Wed, Jul 6, 2016 at 11:03 PM, Chuong, Patrick <pchu...@ti.com> wrote:

> Filed, please reassign if it is filed incorrectly.
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=497424
>
> Patrick
>
>
>
> *From:* wtp-dev-boun...@eclipse.org [mailto:wtp-dev-boun...@eclipse.org] *On
> Behalf Of *Chuong, Patrick
> *Sent:* Wednesday, July 06, 2016 4:53 PM
>
> *To:* General discussion of project-wide or architectural issues.
> *Subject:* Re: [wtp-dev] Debugging Javascript - No source found
>
>
>
> Our application works for nodewebkit and online. The source is the same
> for both online and offline, and we start the underline webserver in the
> nodewebkit case by using require in the index.html page load the backend
> javascript within the node_modules folder.
>
> The backend javascript is the main application where I want to be able to
> debug in the online case, which is in the node_modules folder.
>
>
>
> I’ll file a Bugzilla for this and thanks for having this fix for neon sr1.
>
>
>
> Regards,
>
> Patrick
>
>
>
> *From:* wtp-dev-boun...@eclipse.org [mailto:wtp-dev-boun...@eclipse.org
> <wtp-dev-boun...@eclipse.org>] *On Behalf Of *Ilya Buziuk
> *Sent:* Wednesday, July 06, 2016 4:44 PM
> *To:* General discussion of project-wide or architectural issues.
> *Subject:* Re: [wtp-dev] Debugging Javascript - No source found
>
>
>
> Could you please create a bugzilla for allowing launch shorcuts for js
> files inside node_modules ?  (the fix is trivial and it will heal source
> lookup issue for this case, but we will be able to deliver it only in
> Neon.1 - September 2016). Also, could you explain the reason why do you
> have main js file in node_modules? I'm still a bit baffled with this
> use-case, due to the fact that node_modules folder is typically added to
> .gitignore
>
>
>
> On Wed, Jul 6, 2016 at 10:21 PM, Chuong, Patrick <pchu...@ti.com> wrote:
>
> I have an use case where my main application javascript file is within the
> node_modules folder. It is placed there for a reason and I hope I don’t
> have to move it outside of the node_modules folder.
>
> Yes, eclipse can find source in the node_modules if my main script is
> outside of the node_modules. However, if the main script is inside the
> node_modules, source lookup failed and breakpoint also failed.
>
>
>
> Patrick
>
>
>
> *From:* wtp-dev-boun...@eclipse.org [mailto:wtp-dev-boun...@eclipse.org] *On
> Behalf Of *Ilya Buziuk
> *Sent:* Wednesday, July 06, 2016 4:07 PM
> *To:* General discussion of project-wide or architectural issues.
> *Subject:* Re: [wtp-dev] Debugging Javascript - No source found
>
>
>
> Hello, Patrick
>
>
>
> I am debugging a script within the node_modules folder, and I am hitting
> the no source found editor. Tried adding many different source lookup
> container and non of them work.
>
> I also noticed the launch debug context menu is missing in the Project
> Explorer when right clicking on a JavaScript file in the node_modules
> folder.
>
>
>
> "Run As / Debug As Node.js" shortcuts were deliberately excluded from
> node_modules and bower_components folders for js files. Could you please
> explain the use-case of debugging lib / framework dependency separately
> from the app ?
>
> In terms of source lookup - can you debug scripts from node_modules when
> you start debugging on app's main js file via "Debug As Node.js
> Application" shortcut ? (source lookup should be tuned automatically for
> this case)
>
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Debugging Javascript - No source found

[Ilya Buziuk]

Could you please create a bugzilla for allowing launch shorcuts for js
files inside node_modules ?  (the fix is trivial and it will heal source
lookup issue for this case, but we will be able to deliver it only in
Neon.1 - September 2016). Also, could you explain the reason why do you
have main js file in node_modules? I'm still a bit baffled with this
use-case, due to the fact that node_modules folder is typically added to
.gitignore

On Wed, Jul 6, 2016 at 10:21 PM, Chuong, Patrick <pchu...@ti.com> wrote:

> I have an use case where my main application javascript file is within the
> node_modules folder. It is placed there for a reason and I hope I don’t
> have to move it outside of the node_modules folder.
>
> Yes, eclipse can find source in the node_modules if my main script is
> outside of the node_modules. However, if the main script is inside the
> node_modules, source lookup failed and breakpoint also failed.
>
>
>
> Patrick
>
>
>
> *From:* wtp-dev-boun...@eclipse.org [mailto:wtp-dev-boun...@eclipse.org] *On
> Behalf Of *Ilya Buziuk
> *Sent:* Wednesday, July 06, 2016 4:07 PM
> *To:* General discussion of project-wide or architectural issues.
> *Subject:* Re: [wtp-dev] Debugging Javascript - No source found
>
>
>
> Hello, Patrick
>
>
>
> I am debugging a script within the node_modules folder, and I am hitting
> the no source found editor. Tried adding many different source lookup
> container and non of them work.
>
> I also noticed the launch debug context menu is missing in the Project
> Explorer when right clicking on a JavaScript file in the node_modules
> folder.
>
>
>
> "Run As / Debug As Node.js" shortcuts were deliberately excluded from
> node_modules and bower_components folders for js files. Could you please
> explain the use-case of debugging lib / framework dependency separately
> from the app ?
>
> In terms of source lookup - can you debug scripts from node_modules when
> you start debugging on app's main js file via "Debug As Node.js
> Application" shortcut ? (source lookup should be tuned automatically for
> this case)
>
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Debugging Javascript - No source found

[Ilya Buziuk]

Hello, Patrick

I am debugging a script within the node_modules folder, and I am hitting
> the no source found editor. Tried adding many different source lookup
> container and non of them work.
>
I also noticed the launch debug context menu is missing in the Project
> Explorer when right clicking on a JavaScript file in the node_modules
> folder.
>

"Run As / Debug As Node.js" shortcuts were deliberately excluded from
node_modules and bower_components folders for js files. Could you please
explain the use-case of debugging lib / framework dependency separately
from the app ?
In terms of source lookup - can you debug scripts from node_modules when
you start debugging on app's main js file via "Debug As Node.js
Application" shortcut ? (source lookup should be tuned automatically for
this case)


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

Re: [wtp-dev] Debugging a node program

[Ilya Buziuk]

Hello, Dobrin
there is no additional step required for setting breakpoint and it is
definitely not a node version limitation.

On Tue, Jul 5, 2016 at 10:55 PM, Gorkem Ercan 
wrote:

>
> Do you have any validation errors on the file that you are setting the
> breakpoint on?
> —
> Gorkem
>
>
> On 5 Jul 2016, at 16:34, Alexiev, Dobrin wrote:
>
> Hello,
>>
>> I just tried using Eclipse Neon and wanted to debug a small node app.
>> I tested the Windows version with the latest node runtime (v.4.4.7) and I
>> had no issues. Everything worked.
>>
>> When I tried the Linux version it did not find my current node
>> installation automatically. I had installed it in its default location
>> HOME/.nvm/v0.10.26/bin/node.
>> Once I added the node path to my "JavaScript Runtimes" from the
>> preference page I was able to debug my project.
>>
>> But I was not able to add breakpoints. Every time I click in the editor's
>> selection margin I see an error message "A valid location could not be
>> found for the breakpoint".
>> Is this a node version limitation, or I need to setup something to be
>> able to add breakpoints while debugging?
>>
>> Regards
>> Dobrin
>> ___
>> wtp-dev mailing list
>> wtp-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Fwd: [epp-dev] Neon RC2 packages

[Ilya Buziuk]

On Mon, May 30, 2016 at 11:17 AM, Mickael Istria  wrote:

> Thanks for the info Eugene.
> About IP and license, would it be possible for JSDT to embed such a TS
> server to generate an AST-ish that we could use for such
> navigation/refactoring operations?
>

As I recall, CQ for shipping node is already opened but not yet approved. I
guess, if it will be approved the next logical  step will be opening CQ for
using tsserver. Anyway, It looks like support of language services in JSDT
is not going to happen early than Oxygen.  For Neon.1 the plan is to
replace esprima with closure compiler, while still using DOM AST model
(converting from Closure's Internal Representation will be required).

Looking at the current state of JSDT, it seems like most features depending
> on AST are broken. So there are 2 ways to go AFAIK: dropping the legacy AST
> and using another model (such as the TS one) directly, or having the
> parsers populating an AST. I feel like the first one is more sustainable and
>


> requires more effort.
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat 
> My blog  - My Tweets
> 
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Fwd: [epp-dev] Neon RC2 packages

[Ilya Buziuk]

Mickael, thanks for reporting. I will take a look

On Fri, May 27, 2016 at 11:40 AM, Mickael Istria  wrote:

> I found an important issue with the JavaScript package:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=494731
> Despite not being too annoying at usage, it gives a bad impression to
> users and may pollute the error reporting results.
>
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat 
> My blog  - My Tweets
> 
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Neon M7 New and Noteworthy content

[Ilya Buziuk]

Hello, Chuck
Please, find gerrit change[1] for  Node.js M7 N

[1] https://git.eclipse.org/r/#/c/72158/

On Wed, May 4, 2016 at 7:16 PM, Chuck Bridgham  wrote:

> Hi,
>
> We are ready to provide N for Neon M7.
> The WTP website repo is now Gerrit enabled, and you can find the patch to
> create the empty M7 templates here: https://git.eclipse.org/r/#/c/72057/
>
> You're welcome to submit changes directly through Gerrit - but you can
> also send me your content this time around because of time constraints.
>
> Please submit your content by Thursday evening.
>
> Content will be posted here:
> https://eclipse.org/webtools/development/news/3.8M7/
>
> Thanks - Chuck
>
> IBM Tools development, Eclipse WTP PMC
> IBM Software Lab - Research Triangle Park, NC
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] JS EPP package missing Run actions

[Ilya Buziuk]

Hi, Chuck

I have already opened one for missing  *node and *node.common bundles and
provide a gerrit change.
Bug 490618 - org.eclipse.wst.jsdt.nodejs.feature is missing node plugins[1]

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=490618

On Tue, Mar 29, 2016 at 8:56 PM, Chuck Bridgham <cbrid...@us.ibm.com> wrote:

> Hi Ilya, Mickael,
>
> I also noticed this in the JEE package, and will open a bugzilla to track
> getting this feature included in the core JSDT feature.
> This is just an issue with JSDT M6 I believe (same with the  chromium
> feature not included by default).
>
> I don't think any EPP changes should be needed for M7
>
> Thanks - Chuck
>
> IBM Tools development, Eclipse WTP PMC
> IBM Software Lab - Research Triangle Park, NC
>
>
>
> From:Ilya Buziuk <ibuz...@redhat.com>
> To:"General discussion of project-wide or architectural issues." <
> wtp-dev@eclipse.org>
> Date:03/29/2016 01:41 PM
> Subject:Re: [wtp-dev] JS EPP package missing Run actions
> Sent by:wtp-dev-boun...@eclipse.org
> --
>
>
>
> Hello, Mickael
> it looks like "org.eclipse.wst.jsdt.nodejs.feature" (bower, npm, grunt,
> gulp are there)  is not presented in the epp.product / I would really like
> to make a contibution but I will be off till Friday due to relocation
>
> On Tue, Mar 29, 2016 at 8:26 PM, Mickael Istria <*mist...@redhat.com*
> <mist...@redhat.com>> wrote:
> Hi all,
>
> So there we are, there is now an EPP package for JavaScript and Web
> developer. That's a good thing!
> The main issue I noticed in this package is the lack of "Run actions" for
> JavaScript in general. For example, right-click on a package.json or a
> Grunt doesn't even show a Run As menu. Can someone please have a look and
> suggest which features could be missing, and even contribute the patch to
> org.eclipse.epp.packages ;) ?
> --
> Mickael Istria
> Eclipse developer at *JBoss, by Red Hat* <http://www.jboss.org/tools>
> *My blog* <http://mickaelistria.wordpress.com/> - *My Tweets*
> <http://twitter.com/mickaelistria>
>
> ___
> wtp-dev mailing list
> *wtp-dev@eclipse.org* <wtp-dev@eclipse.org>
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> *https://dev.eclipse.org/mailman/listinfo/wtp-dev*
> <https://dev.eclipse.org/mailman/listinfo/wtp-dev>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] JS EPP package missing Run actions

[Ilya Buziuk]

Hello, Mickael
it looks like "org.eclipse.wst.jsdt.nodejs.feature" (bower, npm, grunt,
gulp are there)  is not presented in the epp.product / I would really like
to make a contibution but I will be off till Friday due to relocation

On Tue, Mar 29, 2016 at 8:26 PM, Mickael Istria  wrote:

> Hi all,
>
> So there we are, there is now an EPP package for JavaScript and Web
> developer. That's a good thing!
> The main issue I noticed in this package is the lack of "Run actions" for
> JavaScript in general. For example, right-click on a package.json or a
> Grunt doesn't even show a Run As menu. Can someone please have a look and
> suggest which features could be missing, and even contribute the patch to
> org.eclipse.epp.packages ;) ?
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat 
> My blog  - My Tweets
> 
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] JSDT grunt / gulp demo - part 1

[Ilya Buziuk]

Hello, guys 
You might know that JSDT team is working on grunt / gulp support. The plan is 
to contribute those plugins to M6 release.
Basically, the work has started and I want to share a short demo video with you 
[1]. For now it is pretty half-baked but 
essential improvements are on the go:

- Launch Configuration for gulp / grunt 
- Navigation from Project Explorer to Editor
- Contribution of tasks to Outline view

If you are interested in this plugins it would be great if you put your 
comments / remarks / proposals into bugzilla [2]
P.S. Sending this email before JSDT Weekly Sync for IBM guys, so that you will 
be able to get the demo before the meeting ;-)

[1] https://vimeo.com/152185558 
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=483399
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] JSDT grunt / gulp demo - part 1

[Ilya Buziuk]

Hey, Angelo

For now (M5 / M6) release we have no grunt / gulp debugger in the plan. So, it 
looks like it will not happen in Neon.
However, we are planning to add Node.js debugger, so in the long run we might 
adjust it to grunt / gulp 

- Original Message -
From: "Angelo zerr" <angelo.z...@gmail.com>
To: "General discussion of project-wide or architectural issues." 
<wtp-dev@eclipse.org>
Sent: Tuesday, January 19, 2016 7:54:34 PM
Subject: Re: [wtp-dev] JSDT grunt / gulp demo - part 1

Hi Ilya, 

Many thanks for this demo. Have you planned to support debugging of Gup/Grunt 
tasks? 

Regard's Angelo 

2016-01-19 16:37 GMT+01:00 Ilya Buziuk < ibuz...@redhat.com > : 


Hello, guys 
You might know that JSDT team is working on grunt / gulp support. The plan is 
to contribute those plugins to M6 release. 
Basically, the work has started and I want to share a short demo video with you 
[1]. For now it is pretty half-baked but 
essential improvements are on the go: 

- Launch Configuration for gulp / grunt 
- Navigation from Project Explorer to Editor 
- Contribution of tasks to Outline view 

If you are interested in this plugins it would be great if you put your 
comments / remarks / proposals into bugzilla [2] 
P.S. Sending this email before JSDT Weekly Sync for IBM guys, so that you will 
be able to get the demo before the meeting ;-) 

[1] https://vimeo.com/152185558 
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=483399 
___ 
wtp-dev mailing list 
wtp-dev@eclipse.org 
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit 
https://dev.eclipse.org/mailman/listinfo/wtp-dev 


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