Tony,
I have looked at JSHint problem. Here is what I’ve found:
1. They are using com.eclipsesource.json (minimal-json) code
2. They have added they’re own custom class to it and slightly modifed the rest
3. They are exporting that modified minimal-json package as com.eclipsesource.json;version=”0.9.0″
4. Tern makes a usage of version “0.9.1” of minimal-json and such bundle is present in MyEclipse with export com.eclipsesource.json;version=”0.9.1″
5. JSHint UI plugin imports com.eclipsesource.json;version=”0.9.0″ and expects it to contain modifications, but “0.9.1” is provided as it is newer and better from OSGi point of view.
Looks like JSHint guys made a mistake here (this time not our fault – uff ;). They should export a package in a way to mark the changes they did (add qualifier, e.g. “special”) and then make sure they import precisely that package (import with range [0.9.0.special, 0.9.0,special]). I will now make a contribution to JSHint repository and you will be able to get a fix as soon as they fix the issue. I will provide you with the link to pull request so you can vote.