rsingla / jslint4java

Automatically exported from code.google.com/p/jslint4java
Other
0 stars 0 forks source link

jslint4java is definitely not thread-safe #97

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create a JSLint instance for all threads
2. Call jslint.lint(...).getIssues() from multiple threads
3. See the weird output

What is the expected output? What do you see instead?
Since http://code.google.com/p/jslint4java/issues/detail?id=47 jslint4java 
should be thread-safe, using thread-common JSLint instance and calling .lint() 
from threads should not produce any problems.

What version of the product are you using? On what operating system?
JSLint4Java 2.0.3
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)
Linux amd64

Original issue reported on code.google.com by hangcsa...@gmail.com on 7 May 2013 at 9:14

GoogleCodeExporter commented 9 years ago
Please see issue 94.  This is an ongoing change to make it thread safe, and is 
not yet present in ant released version.

Original comment by d...@happygiraffe.net on 7 May 2013 at 2:50

GoogleCodeExporter commented 9 years ago
"…any released version"

Original comment by d...@happygiraffe.net on 7 May 2013 at 2:50

GoogleCodeExporter commented 9 years ago
Thanks for the info! Keep up the good work! ;)

Original comment by hangcsa...@gmail.com on 7 May 2013 at 8:23