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.
Difference between revisions of "JSDT/Confcalls/Minutes 20151110"
(One intermediate revision by the same user not shown) | |||
Line 22: | Line 22: | ||
Orlando Rincon | Orlando Rincon | ||
Victor | Victor | ||
+ | Doug Schaffer | ||
== Meeting Minutes == | == Meeting Minutes == | ||
Line 34: | Line 35: | ||
## More work ongoing to avoid virtual projects | ## More work ongoing to avoid virtual projects | ||
## CQ process to be started to include in JSDT | ## CQ process to be started to include in JSDT | ||
+ | # We will consider deprecation and removal per API but as a general rule deprecation on Neon release with an option to remove on Neon+1 is acceptable | ||
+ | # Agreed to have to workspace compatability | ||
+ | # Agreed that it will be possible to drop features on Neon release | ||
+ | # No final decision on parser strategy. The two favored choices are acorn or shift-java. We will learn more about Shift before reaching a decision | ||
+ | # Agreed to move validation to extension points |
Latest revision as of 14:21, 10 November 2015
Logistics
See JSDT/Confcalls
Meeting Agenda
- Updates on current work
- JSON Editor
- npm and bower contribution
- JavaScript Debugger
- Review and discuss conclude proposals for changes on JSDT/JSDTRenewalArchitecture
Attendees
Gorkem Ercan Adalberto Alexey Kazakov Alina Chuck Bridgham Denis Golovin Ilya Buziuk Mickael Orlando Rincon Victor Doug Schaffer
Meeting Minutes
- npm and bower contribution process started
- JSON Editor
- CQ changed to under review
- targeting M2 with this contribution
- Debugger
- Repo with changes https://github.com/jbosstools/chromedevtools
- Still needs to be updated to work with JDST breakpoints
- More work ongoing to avoid virtual projects
- CQ process to be started to include in JSDT
- We will consider deprecation and removal per API but as a general rule deprecation on Neon release with an option to remove on Neon+1 is acceptable
- Agreed to have to workspace compatability
- Agreed that it will be possible to drop features on Neon release
- No final decision on parser strategy. The two favored choices are acorn or shift-java. We will learn more about Shift before reaching a decision
- Agreed to move validation to extension points