Update Eclipse plugin to use latest version of JsTestDriver

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Browse to http://code.google.com/p/js-test-driver/downloads/list
2. Latest version is 1.3.1
3. Browse to http://js-test-driver.googlecode.com/svn/update/
4. Latest versions are 1.1.1.e and 1.1.1.c

What is the expected output? What do you see instead?
I'd like to be able to use the latest version of jsTestDriver with the Eclipse 
plugin, in order to run asynch tests.

What version of the product are you using? On what operating system?
1.1.1.e on Mac OS X 10.6.6 with Aptana Studio 2 built on Eclipse Platform
Version: 3.5.2.R35x_v20100210-0800-9hEiFzmFst-TiEn9hNYgDWg1XN8ulH_JvCNGB
Build id: M20100211-1343

Please provide any additional information below.

Original issue reported on code.google.com by siunmaru on 5 Mar 2011 at 10:46

[GoogleCodeExporter]

Please could someone feed back on when 
http://js-test-driver.googlecode.com/svn/update/ might be updated? Or add a 
wiki article on how to update the plugin manually using the files available at 
http://code.google.com/p/js-test-driver/downloads/list

Original comment by siunmaru on 29 Mar 2011 at 8:45

[GoogleCodeExporter]

Issue 264 has been merged into this issue.

Original comment by corbinrs...@gmail.com on 4 Nov 2011 at 1:49

[GoogleCodeExporter]

Issue 287 has been merged into this issue.

Original comment by corbinrs...@gmail.com on 4 Nov 2011 at 1:49

[GoogleCodeExporter]

Since the last maintainer moved to India to pursue an MBA (which means he is 
dead to us developers. :)) The eclipse plugin has bitrotted. 

I am current working on cleaning out the cruft and getting it going again. It 
should come out with the 1.3.3e release.

Original comment by corbinrs...@gmail.com on 4 Nov 2011 at 1:51

[GoogleCodeExporter]

Cool, I'd abandoned it for that reason - look forward to seeing it up and 
running again. Thanks Corbin

Original comment by siunmaru on 4 Nov 2011 at 2:04

[GoogleCodeExporter]

Issue 292 has been merged into this issue.

Original comment by corbinrs...@gmail.com on 8 Nov 2011 at 11:43

[GoogleCodeExporter]

Issue 293 has been merged into this issue.

Original comment by corbinrs...@gmail.com on 8 Nov 2011 at 3:40

[GoogleCodeExporter]

Corbin, RE comment 4, I would really like to know if you are going to be able 
to release an update of the Eclipse plugin soon.

I looked into JS testing frameworks today. And the JsTestDriver plugin for 
Eclipse is exactly what I want. But, I'm not getting any output in the console. 
The tests run and pass or fail. But, clicking or double-clicking on them gives 
me nothing.

If you have a moment to update us on what the status of the plugin is, I would 
really appreciate it.

Original comment by cfchris on 9 Feb 2012 at 12:26

[GoogleCodeExporter]

Re: comment 8.

The workaround I'm using for the no-message problem with Firefox is to use, 
*cough*, IE when I need to see the failure message. So I have Firefox up to 
debug and IE to see the error message. Not optimal, but usually adequate. 
Clearly that's only relevant for Windows systems. Don't know if Opera would 
work here for this purpose. (Chrome doesn't.)

Re: original issue

I do hope the new plugin isn't permanently bound to a particular version of the 
underlying js-test-driver release. Had this been done from the start, this 
issue would hardly exist. It would also make it feasible to hack on 
js-test-driver if it means not dealing with the overhead of learning the 
Eclipse interfaces and build system.

Original comment by eric.eh9@gmail.com on 9 Feb 2012 at 12:15

[GoogleCodeExporter]

This might be done too with the successful release 1.3.4.e.

Original comment by cfchris on 16 Feb 2012 at 3:13