Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] How do we get JSDT issues that have patches actually fixed ?

On Tue, Jan 29, 2013 at 11:15 AM, Justin Early <earlyster@xxxxxxxxx> wrote:
> Can you be more specific on this issue?
>> the lack of handling semi-colons properly

Both JSDT and VJET report spurious errors for this code

someVar = 1 + 2

For our variant of JSDT [1] we disabled JSDT's problem checking and
instead plan to use an optimized version of JSHint-eclipse [2].


> Thanks,
> Justin
> Sent from my iPad
> On Jan 29, 2013, at 1:58 AM, Max Rydahl Andersen <max.andersen@xxxxxxxxxx> wrote:
>> Hi guys,
>> We got a bunch of fixes/patches submitted in bugzilla trying to get JSDT not fail on common available javascript libraries;
>> especially in context of libraries popular in mobile tools.
>> Similar errors still exist in VJET which has its own fork of JDST so i'm cc'ing vjet-dev on this topic too.
>> Some of these issues and their patches are close to a year old...time to get these pushed in IMO.
>> - NPE in CompilationUnitBinding#sourceMethod() (triggered by birt and other js libraries)
>> - [exceptions] Errors running builder 'JavaScript Validator' on project with ArrayIndexOutOfBoundsException (Also fixes #344745)
>> - [search] ArrayIndexOutOfBoundsException in DiskIndex during problem detection
>> - [exceptions][parser] ArrayIndexOutOfBoundsException in Parser#consumeEmptyStatement on a javascript file when building project
>> - ArrayIndexOutOfBoundsException in UnconditionalFlowInfo#markAsDefinitelyNonNull() with FieldReference
>> - [validation] Eclipse complains about jquery minified JS files
>> These makes it much more tolerable to use JSDT with javascript libraries.
>> One issue we haven't found a way to solve yet is the lack of handling semi-colons properly - but would love to see it fixed but lack the info on how to update/modify the parser.
>> But lets start with what we already got patches for - how do we get these issues with already existing patches fixed for Kepler ?
>> /max
>> _______________________________________________
>> wtp-dev mailing list
>> wtp-dev@xxxxxxxxxxx
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx

John Peberdy

Back to the top