Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

JSDT/Confcalls/Minutes 20160405

< JSDT‎ | Confcalls
Revision as of 13:33, 5 April 2016 by Psuzzi.gmail.com (Talk | contribs) (SWTBot / RCPTT to test JSDT)

JSDT/Confcalls/Minutes 20160405

Attendees : Orlando, Alina, Victor Sosa, Ilya, Adalberto, Gorkem, Patrik, Victor R, Chuck, Mickael

Debugger

Ilya created a Gerrit change to hide the VFS, attached as a Filter, enabled for Chromium 

He is now linking debug to JSDT editor https://bugs.eclipse.org/bugs/show_bug.cgi?id=490626

Nodejs Launcher

Adalberto finished with some port in bugzilla, already +1ed. And now he is looking at different bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=491045

Launch configuration:

  • GE: Did anybody tried to launch the launch configuration?
  • IB: Yes, but you need to have a project in your workspace

Orlando working on UI, to configure JavaScript runtimes (targeted for now to Node.js): https://bugs.eclipse.org/bugs/show_bug.cgi?id=488975

Some extra work is needed on the Node.js application launcher to react to the possibility that a user can now specify its custom Node.js binary.

Include path:

  • GE: Does this work considers also the include path?
  • OR: we can provide arguments, but we might need some tweaks.
  • VR: we'll need to filter out resources, 
  • OR: not during launch, isn'it ?
  • VR: we should have some property file to speficy this
  • OR: indeed, the user will be able to define a file to filter items

JSDT infos

pending changes (excl SSE): https://git.eclipse.org/r/#/q/project:jsdt/webtools.jsdt+is:pending

ES6

Gorkem: We support ES6, in classpath, but not in features

  • VR: do we need to use node in content assist and validator ?
  • GE: in content assist, yes
  • VR: and what about supporting libraries, like in NPM?
  • GE: we should support what is built into Node. (Node core)
  • VR: what if not using Nodejs ?
  • GE: we'll need to have browser runtime and Nodejs runtime i.e. JVM when you have different classlibs
  • VR: will we be able to configure these library at project level ? when ?
  • CB: Actually OR is doing exactly this for static. We can extend and doing this at runtime
  • VR: now is more a java project config, more about project metadata
  • OR: effectively I can configure different launchers, maybe we can open new bugzilla for managing metadata (which is different w.r.yt)
  • CB: That make sense.
  • GE: agree, let's make this in steps. 

Gorkem: working on model test failing from (was) 200 > (now) 30, mostly JDoc. we'll soon have around 500 running tests 

  • GE: Some of the tests are not fixable, for funny reasons

Ian: is making progress with the com*tion engine, is making changes to his architecture

Shane: already sent a gerrit request for Highlighting, which also supports ES6 template literals

Eugene is contributing a fix to the binding in a single file. It is not about inference, but it is a quite a big step.

Eugene also raised a question about providing a pretty accurate suggestion hierarchy, but not very fast. See this [wtp-dev discussion]

Mickael: this build seems to be failing because of Esprima: 

https://git.eclipse.org/r/#/c/69787/ (change) https://hudson.eclipse.org/webtools/job/jsdt-gerrit/353/console (build)

Gorkem: we should have some test in WEB related to Esprima

Failure reason: tests are strict, as they count also on the execution order. 

JSON Editor

Alina is working on really complex scenarios, which are failing i.e. the insertion. 

  • Arrays: All is working expecting JSON Pairs, while for the arrays the method signature expects objects. 
  • JSON quote issue: the double quotes are read in the wrong way. the JSON Tokeniser (JFlex) is not able 

Victor R: we got CQ approval to use icons proposed by RH designers. 

Docs

Gorkem explained Patrik how to setup Nashorn

Patrik wrote https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn and linked it to JSDT / Arch.

SWTBot / RCPTT to test JSDT

Victor Sosa: we're using a RCPTT to test UI, simpler w.r.t. SWTBot. 

  • MI: can it work in Tycho?
  • VS: we can do this via command during the build. 
  • MI: SWTBot has the advantage of being compatible with JUnit. 
  • VS: My impression, RCPTT is easier
  • MI: in any case we need to add RCPTT or SWTBot into the Tycho build
  • VR: What it is required in terms of code compliance?
  • MI: both are Eclipse projects, and we don't need specific Commercial support.
  • VR: we need permissions to change WTP parent/pom.xml
  • PS: it would be good to have reference on how a developer can test locally
  • MI: this is feasible, will provide reference on request
  • PS: and maybe we should have a document comparing RCPTT vs SWTBot
  • VS: I agree on this, it is feasible.

Bottom line: the idea is to enable both SWTBot and RCPTT

  • GE: as suggested by VR, and CB , we should bring this up to WTP and WTP rel-eng.

Other Issues

Victor added Issues on HTML (JSDT Web) , probably Ian could take care of these

a patch from Eugene is waiting 

MI: please welcome contributors for the new YAML editor (see wtp-dev proposal) contributed here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=491050

  • VR: please define, usage, technology, impacts on WTP
  • MI: editor used since long time in JBT, any contribution will be managed via Git
  • There are some IP issues as the project is old and because of many contributors
  • CB: we should not underestimate the impact, and check the quality
  • GE: remember JSON Editor, we had some unexpected issues.

Back to the top