Eclipse JavaScript Development Tools 3.8.0

Release Date
Deliverables

Source code for deliverables tagged in Git as version tagged R3_8_0, viewable in the JSDT Git repositories .

Internationalization

Internationalization and Localization will be supported.

Target Environments

JSDT will support the platforms certified by the Eclipse Platform project. For a list of platforms supported , see Eclipse Target Operating Environments.

Themes

Everything

The following are plan items including those not yet categorized into a theme.

  • Continue the working on Integration of dependency management tools like node.js/bower/npm into JSDT, thus in order to make it possible for developers to use such tools right from the IDE. A number of CQs is created and approved, due to make it possible to invoke native node.js/bower/npm utilities installed in user environment

  • An extension point for configuring and invoking node.js and npm. The default implementation should allow users to select their node/npm installation as preference but tools like JBT should be able to extend and provide embedded/preconfigured node.js implementations.

  • JSON Editor integration contribution is going in order to let developers to create/edit/modify JSON files. From JSDT point of view the goal is to provide a support for bower.json/.bowerrc/packages.json files editing which is a part of dependency management tools integration work.

  • Parser/scanner/validator changes in order to make it compatible to ECMA5 at least (but better to ECMAScript 2015)

  • The maintenance for bug fixing and solving the performance issues like the following:

    • Limit the scope of files to be parsed by JSDT as many of cases don't require all the existing project files to be parsed in all the cases.
    • Work on Performance issues: We've added a way to skip/disable the internal JSDT parsing/validation. Now we need to add an extension mechanism in order to allow external validation.
    • Other performance and stability issues (BugZilla, Automated Error Reporting System, and so on)

  • Provide a solution for an automatic disabling of JSDT internal parsing/validation in case when Tern.java is installed in user's environment, to make JSDT not to consume the resources on parsing/validation/content assisting while this work is doubled and is done better by Tern.java. This could be done by either the configuration of JSDT by a JBT's jst.jsdt plug-in or by Tern.java itself (by its JSDT integration plug-in).

  • Initial contribution of Google Chrome Dev Tools [485188] (target milestone: 3.8 M5)
  • Node.js-based JavaScript Dependency Management Tools: bower, npm [481828] (target milestone: 3.8)
  • JSDoc rendering of doc tags needs improvement [325379] (target milestone: Future)
  • Add ecmascript4 .JavaScript 2 compiler compliance level [223131] (target milestone: Future)
  • jsdt is not fully compatible with JSDoc toolkit [267775] (target milestone: Future)
  • Two validation errors shown in problems view for single syntax error [279009] (target milestone: Future)
  • Open Attached JSDoc throws NPE [300670] (target milestone: Future)
  • Open Attached JSDoc is not compatible with JSDoc-toolkit [300677] (target milestone: Future)
  • false warning reported about missing semicolon before the closing } [304933] (target milestone: Future)
  • Boolean type assumed for || expression [317165] (target milestone: Future)
  • JSDoc3 Interface Support (@interface & @implements) [317928] (target milestone: Future)
  • remove all calls to printStackTrace [319851] (target milestone: Future)
  • Unexpected "Unexpected Tag" warnings in JSDoc [319880] (target milestone: Future)
  • Confusing 'Missing semicolon' warnings [324673] (target milestone: Future)
  • Jsdoc support for optional parameters [333276] (target milestone: Future)
  • JSDoc is not shown for the class properties [333712] (target milestone: Future)
  • Invalid errors on switch statement case expressions for mismatched types [335630] (target milestone: Future)
  • Regular Expression Error Handling Improvement Request [336579] (target milestone: Future)
  • multiple jsdoc argument types lead to exception [343052] (target milestone: Future)
  • jsdoc-toolkit array notation is not supported [350928] (target milestone: Future)
  • JSDoc on Array [421322] (target milestone: Future)
  • Bower IDE contribution [459732] (target milestone: Future)