I'd like to add the following issue to
this list to be reviewed:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=404832- _javascript_
error on valid regex
as a one of pretty important problem with many _javascript_s like
jQuery.
The issue has a patch proposed.
Thanks,
Victor Rubezhny,
Exadel, Inc.
On 05/28/2013 04:45 PM, Christopher Jaun wrote:
We started reviewing all the
patches contributed to JSDT last week and plan to begin
delivering them to the 3.5.1 maintenance shortly.
Thanks,
Chris
Max Rydahl Andersen ---05/28/2013
03:01:37 AM---Hey, I tried sending this earlier but had issues
with my mail adress setup for eclipse.org mailing l
From: Max Rydahl Andersen
<manderse@xxxxxxxxxx>
To: "General discussion of proje..."
<wtp-dev@xxxxxxxxxxx>,
Date: 05/28/2013 03:01 AM
Subject: [wtp-dev] Getting JSDT issues fixed
?
Sent by: wtp-dev-bounces@xxxxxxxxxxx
Hey,
I tried sending this earlier but had issues with my mail
adress setup for eclipse.org mailing lists.
Over the last two release trains, and especially the last one
my team from Red Hat/JBoss have opened, commented and attached
patches
to bugs to get fixed in JSDT (_javascript_) - at least enough
to make it tolerable to use with todays _javascript_ libraries.
A lot these are not fixed yet, even though there were many
promises on getting them integrated over the last many
quarters.
A few of these are mainly just about getting JSDT to not
report false positivs
in its error reports and not fail on common available
_javascript_ libraries
(jquery, jquery mobile minified is especially hurt - and those
are probably
some of the most used libaries).
Is there any chance of getting at least some of these issues
fixed so JSDT not for the third year will scare away
mobile/_javascript_ developers ?
Here are the current list of issues we got collected:
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=344745 - [search] ArrayIndexOutOfBoundsException in
DiskIndex during problem detection
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
https://bugs.eclipse.org/bugs/show_bug.cgi?id=349020 - [validation] Eclipse complains about jquery
minified JS files
Links to past discussions concerning JSDT patches/issues the
last two release trains:
http://www.mail-archive.com/wtp-dev@xxxxxxxxxxx/msg06207.html - last big ping
http://www.mail-archive.com/wtp-dev@xxxxxxxxxxx/msg06216.html - Former JSDT lead stating he would look at _ALL_ of
these bugs to be included in M6 or sooner
http://www.mail-archive.com/wtp-dev@xxxxxxxxxxx/msg06325.html - Paul Verest questioning JSDT future
http://www.mail-archive.com/wtp-dev@xxxxxxxxxxx/msg06298.html - improvements to JSDT via NJSDoc
http://www.mail-archive.com/wtp-dev@xxxxxxxxxxx/msg06034.html - thread about patches to JSDT is accepted but have
to fit within project scope
What can we do to get these fixed ? note, these are not API
changes afaics - just pure bugfixes and stop-gap fixes to make
JSDT feasible to use and not
get in the way of majority of _javascript_ users.
Thank you,
/max
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev