rsingla / jslint4java

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

Configuration update has no effect after applying #77

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Updating the jslint4java configuration in Eclipse (e.g. enable or disable the 
[eqeqeq] check) and hitting Apply, then Ok doesn't have effect on the list of 
current 'Problems'. The configuration does not trigger a new validation.

Even closing and re-opening the javascript file that contains the 'Problems' 
doesn't trigger a new validation. I would assume the validation results are 
cached.

Choosing "Disable jslint4java" on the project, and re-enable it does trigger a 
new validation with the updated configuration.

It would be nice if the Apply button would have this effect as well.

Original issue reported on code.google.com by kees...@gmail.com on 4 Feb 2012 at 10:42

GoogleCodeExporter commented 9 years ago
This is the eclipse plugin, right?

https://github.com/happygiraffe/jslint4java-eclipse

I'll take a look.  It was definitely working last time I looked…

Original comment by d...@happygiraffe.net on 6 Feb 2012 at 8:30

GoogleCodeExporter commented 9 years ago
Aw, filed the bugs in the wrong project. Indeed, that's the one. bug #76 was 
related to that project as well.
Let me know if I should move the bugs to the github bugtracker.

Original comment by kees...@gmail.com on 6 Feb 2012 at 8:59

GoogleCodeExporter commented 9 years ago
I'll be quite up-front: I've not done much with that project, as I've failed to 
come up with a way to actually build it outside of Eclipse.  All the 
instructions for eclipse and ant/maven are completely baroque. :(

Original comment by d...@happygiraffe.net on 6 Feb 2012 at 9:25