Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
JSDT/Confcalls/Minutes 20160329
Contents
JSDT/Confcalls/Minutes 20160322
Attendees: Gorkem, Ilya, Patrik, Adalberto, Alina, Ian, Orlando, Victor Sosa, Victor Rubezhny, Alexey
Debugger
Ilya is working on Debugger over VFS. He is splitting the effort in two bugzillas
Ilya also discussed with Adalberto how to implement the the Launch config for Node. The first thing to do is to give the uset the option to select a debug port, as an example the default 5858.
Gorkem suggests to add Host information, using an URL abstraction, like "<host-address>:<port>" .
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=490208
Notes:
- now the debugger is working on the ASTVisitors directly.
- The Breakpoints are now working in Gulp
Nodejs
Almost all the Gerrit changes for Nodejs are in. Only some tests are still pending
JSON Editor
Alina working on a bug related to JSON Arrays. This is caused by the current implementation, which is is empty. Alina is also facing more complex scenarios, as an example: when inserting child nodes.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=486860
Victor Created CQs for adding icons created by RH designers.
An engineer from QE who added new bugs related to JSON error. Those bug are simple
[COMPLETE, add bug references]
ES6
After switching to the new parser there is some minor debug issue.
- As an example: The Nashorn "classpath hook" it is not friendly to Tycho. > so we removed the Nashorn API export, and added the dependency to the JSDT Core project.
Gorkem is preparing to send an email to WTP-dev, in order to explain this.
Patrik is going to write documentation explaining how we are hooking the Nashorn libraries.
There is another new contributor, Eugene Melekhov, who is helping to work on the Compiler / Parser. See the discussion by Searching mailman for : "[wtp-dev] JSDT Parser"
see also: https://dev.eclipse.org/mhonarc/lists/wtp-dev/msg09767.html
JSDT Setup
Ian used tutorial to setup the development env. The tutorial works, except for the Nashorn cp hook, which required some work
Validator
Victor there is the need to make some changes to SSE for use the Validator on documents that are not "structured documents". You can see a change (Gerrit review pending)
The Gerrit change is solving some old issues.
The old Java (Script) Reconcilier it is unclear and it should be deprecated
EPP Package
We broke the release train, while moving to JSDT 2.0
Orlando: There are several plugins missing from the package, as an example: nodejs, debug, etc.
Ilya: Maybe because of jsdt.node feature. If you search you can see that no tags are used: so The EPP package is built from the Master
Ilya pushed a change to include node and node.common in the feature See https://bugs.eclipse.org/bugs/show_bug.cgi?id=490618
For SimRel we're giving the repo for JSDT
we'll probably need to ask WTP a respin, maybe Chuck can help. He'll decide as Project Lead
Gorkem: maybe we can ask Mickael to create a N-Build for JSDT.
The idea is : We need a way to kick an EPP Build > This will make testing easier
Action: Gorkem is to Ask Mickael what are the options .
Docs
Patrik edited "Missing WTP Web docs": See https://bugs.eclipse.org/bugs/show_bug.cgi?id=477020
Patrik will update WTP Web pages by updating Link to N&N
Lars Vogel suggested to enable Gerrit for WTP web site, Chuck is already aware of this See https://bugs.eclipse.org/bugs/show_bug.cgi?id=490396
RelEng
Patrik is working to add a JSDT rel-eng folder, containing target platforms, project sets, launch configurations for JSDT. See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486944
Note: JSDT-releng folder is now under the wtp-releng aggregator project, as the wtp-releng .parent pom contains updated links to p2 repositories used in WTP.
- Patrik is to send an email to WTP-dev, asking where to put a rel-eng folder in
Other
Orlando started working on UI for Javascript Frontend
Chuck asked what will be included in the next Milestone (M7)
> Gorkem idea is that for M7 we should finish what we started in M6. So, we are happy if Debugger, JSON Editor and ES6 will work.
Anything new will basically be delayed to Oxygen, as an example LIntern, ..