[jbosstools-dev] VJET vs https://bitbucket.org/nexj/webtools.jsdt.core/ ?

[Gorkem Ercan]

The version I have played was almost the very initial version and it actually did a better job on certain places (as advertised). I have been following up with the commits and a steady flow of improvements were coming in. Unfortunately I did not find the time to play with the late builds. 
--
Gorkem


On Feb 11, 2013, at 12:38 PM, Victor Rubezhny <vrubezhny at exadel.com> wrote:

> Yes, Max.
> I follow the wtp-dev mailing lists and told on this alternative at F2F Meeting in Brno.
> This requires to have a modified Rhino to be shipped along with this fork of JSDT. John Peberdy asked wtp-people for feedback on his JSDT-fork. They told that they aren't interested in getting the JS objects info by executing the scripts.
> 
> At the moment the fork is not a candidate to be a proposal for eclipse.
> 
> JSDT Validation Builder is disabled (at least proposed to be made disabled) on a project because the fork has (if I'm correct) its own validation. So probably it true that its validation is less strict than the JSDT one.
> 
> Gorkem played with this project in days of F2F Meeting. Probably he's able to say more.
> 
> Victor
> 
> 
> On 02/11/2013 08:12 PM, Max Rydahl Andersen wrote:
>> Hi,
>> 
>> After I nudge on WTP-dev to get eclipse JSDT issues we got patches for included in M6 I realized
>> there is now also https://bitbucket.org/nexj/webtools.jsdt.core/ as an alternative to VJET.
>> 
>> Victor/Denis - have you looked/tried that ? (see wtp-dev mailing list for discussions about it)
>> It seem to be less strict in its java script checking.
>> 
>> /max
>> 
>