Follow up...
I have gone through these bugs and commented on each of them.
Out of this list there is one bug that VJET shares.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=349020
There is one bug that is not applicable to VJET (right now) due to feature difference.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=344745 - [search] ArrayIndexOutOfBoundsException in DiskIndex during problem detection
The others are JSDT only bugs and not shared by VJET
https://bugs.eclipse.org/bugs/show_bug.cgi?id=366247 - NPE in CompilationUnitBinding#sourceMethod() (triggered by birt and other js libraries) https://bugs.eclipse.org/bugs/show_bug.cgi?id=356446 - [exceptions] Errors running builder '_javascript_ Validator' on project with ArrayIndexOutOfBoundsException (Also fixes #344745) https://bugs.eclipse.org/bugs/show_bug.cgi?id=350693 - [exceptions][parser] ArrayIndexOutOfBoundsException in Parser#consumeEmptyStatement on a _javascript_ file when building project https://bugs.eclipse.org/bugs/show_bug.cgi?id=357353 - ArrayIndexOutOfBoundsException in UnconditionalFlowInfo#markAsDefinitelyNonNull() with FieldReference
As far as Kepler there is no plan to get VJET put into Kepler right now. VJET is currently in incubator.
JustinHi John,
Thanks for the feedback.
Yes I see the syntax error in VJET too... created bug for this.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=399417
Thanks for the info didn't see this case in our test suite.
For this
For our variant of JSDT [1] we disabled JSDT's problem checking and instead plan to use an optimized version of JSHint-eclipse [2].
Do you see any issues with performance? JSDT has to parse the js file for search and code assist, then jshint has to parse and report issues.
Justin
_______________________________________________ vjet-dev mailing list vjet-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/vjet-dev
|