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 20160119
Logistics
See JSDT/Confcalls
Attendees
Gorkem, Chuck, Victor Rubezhny, Patrik Suzzi, Ian, Alina, Orlando Rincon, Denis Golovin, Ilya, Victor Sosa
Meeting Notes
- Debugger:
- All debugger bundles are on the JSDT repo
- support WIP 1.0, WIP 1.1
- Integration test bugzillas exists. We need to find out about testing against real browsers and node.js (in eclipse it is a problem, another option is running out of Eclipse, on a Travis instance)
- [Victor and Denis] Update JSDT feature to include chrome based debugger.
- Issues in bugzilla related to Neon release work:
- All debugger bundles are on the JSDT repo
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485603 Generate Development Web Inspector Protocol Backend Plugin for Chrome Canary https://bugs.eclipse.org/bugs/show_bug.cgi?id=485604 Generate Web Inspector Protocol Backend Plugin v1.1 for Chrome Stable https://bugs.eclipse.org/bugs/show_bug.cgi?id=485605 Include JavaScript Debugger for Chrome/Chromium into build https://bugs.eclipse.org/bugs/show_bug.cgi?id=486057 Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace https://bugs.eclipse.org/bugs/show_bug.cgi?id=486058 Browser tab should be locked when VM suspended at break point in Chromium Debugger https://bugs.eclipse.org/bugs/show_bug.cgi?id=486061 Translate breakpoints from .js files to Chromium/Node V8 JavaScript Engine https://bugs.eclipse.org/bugs/show_bug.cgi?id=479466 Support for node.js debugging https://bugs.eclipse.org/bugs/show_bug.cgi?id=486065 Support Chromium based browser debugging https://bugs.eclipse.org/bugs/show_bug.cgi?id=486066 Launch Configuration for Browser based applications https://bugs.eclipse.org/bugs/show_bug.cgi?id=486074 JavaScript Debugger integration tests for chromium based browsers https://bugs.eclipse.org/bugs/show_bug.cgi?id=486075 Java Script Debugger integration tests for node.js
- Treating node.js as a runtime. Similar to what JDT does with JVMs. Gorkem will create bugzilla(s) for this work.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=359436
- As example: run configurations
- Gulp/Grunt:
- Next work is on launch configurations, navigation, and gulp multiple files
- All contributors are recommended to Follow up with wtp-releng mailing list for code freeze periods.
- JSON Editor:
- Is not included on the features, Victor will work on a fix
- extension point for schemas so that they are used from a single editor.
- Patrik Suzzi is editing the https://wiki.eclipse.org/JSDT/Development , to explain development environment setup. this is the bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486037. Will need some comments to understand which are the most used plug-ins for JSDT development
- Ian and Shane from Red Hat has gone through the process of setting up the environment. They can probably provide feedback
- Should we have a new TP for JSDT ( or WTP) development.
- JavaScript validation
- initial contribuiton
https://git.eclipse.org/r/64672
- HTML/CSS validation is seeking a reviewer from SSE
https://bugs.eclipse.org/bugs/show_bug.cgi?id=443097
- Please review the code for the proposal at https://git.eclipse.org/r/63093
- Esprima CQ: http://dev.eclipse.org/ipzilla/show_bug.cgi?id=10691