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 20151208
Logistics
See JSDT/Confcalls
Attendees
Ilya, Chuck, Orlando, Alina, Alexey, Victor
Meeting Minutes
- JSON Editor
- Angelo (the author) has pushed the first patch set into Gerrit.
- There is an issue in .gitignore which disabled the .project files to be uploaded. Angelo is going to provide another patch set to the end of the week.
- Victor is working on maven project setup and feature creation/update for JSON Editors
- Orlando/Alina may browse the code and start review/test for the contribution (taking into account that .project files are to be manually created)
- If no other objections (upon the fixing the issue listed above) we still should ask Nick (SSE lead) for a review
- Related bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=471820
- npm and bower contribution
- Code has dropped to master and is available for download and installation from the latest declared build at http://download.eclipse.org/webtools/downloads/drops/R3.8.0/I-3.8.0-20151207010029
- Ilya working on improvements regarding more generic launch configurations on JSDT repository
- Is a part of M4 release
- Related bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=481828
- Grunt & Gulp work
- CQs for Grunt and Gulp non-exempt have been created and approved by PMC Member:
- Bugzilla for Grunt https://bugs.eclipse.org/bugs/show_bug.cgi?id=483398
- Bugzilla for Gulp https://bugs.eclipse.org/bugs/show_bug.cgi?id=483399
- JavaScript Debugger
- Chromuim.org and Google have accepted the proposal to publish Chrome Development Tools under the EPL license. As such, the following CQ is filled with an updated source code archive, new licensing policies and a link to updated original repo, and already is under the review:
- Denis is to prepare the updated patch set for Gerrit based on the latest original Chrome Development Tools repository.
- Bugzilla for ChDT: https://bugs.eclipse.org/bugs/show_bug.cgi?id=479466
- Parser replacement
- All are agreed that it's going to be critical and we need to have a plan (tied to the comming WTP milestones) for ongoing changes for JSDT Core
- Victor is trying to use Esprima parser in order to get an ESTree AST from Esprima (in order to create a dom.ast model) as well as more simplified object's list of lexical tokens (in order to use it for syntax highlighting).