New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues #99 and #95 . Linkage error or class not found fixed. #100
Conversation
… not found fixed.
Please get this into a build a.s.a.p. The MyEclipse team are adding a LOT of javascript functionality at present and this would be an awesome addition as it stops me adding this tools to the latest bleeding edge version in their CI stream. This topic refers: |
👍 But we need to wait for @ralfstx Ralf I can release, if Ralf happens to be away for long |
Big Thx. |
Will look at it today |
I was a bit ahead of time, built and bundled as now waiting for official binary |
The tool suite looks great. |
Thanks @tonyherstell! |
@ralfstx Ralf, it was @piotrtomiak Piotr who actually sent PR |
Quite right. |
I'm sorry for mixing that up! Thanks @piotrtomiak! |
I am sure he wont mind :) |
:-) |
You're welcome guys! OSGi can be very tricky ;) |
This should fix the LinkageError or at least the ParseException I have reported in Issue #99. Basically, what I found is that jshint.ui was not using json implementation from jshint plugin, but possibly some other version (provided by Tern or NodeJS). Altough this commit should fix the issue for JSHint, installing JSHint it into Eclipse still may brake other plugins, since the shipped json package is modified. The full solution here would be to put modified version of json package into a different package (like e.g. com.eclipsesource.jshint.json). This would help avoid confusion.