No yellow marks for compiler warnings #346
Comments
|
I think that the problem is that Eclipse requires Java 11 since 4.17 and erlide is still using java 8. I have a branch where I updated the java version, but it's a bit tricky because also maven and other tools need updates and I'm not sure if I can test it all. There is also a possible issue if you have Erlang 25 installed, as it can't load beam files compiled with older versions (it's possible that even Erlang 24 has issues). Rebuilding that part will be a lot of work and some features will probably be dropped (most importantly, the debugger). Unfortunately I am not really maintaining this project anymore, and as time went by it is harder and harder to bring it back in sync with Java and Erlang... |
|
Ok, thanks for many hints. I will try out some combination that works reasonably well. I haven't got into OTP 25 yet at least... |
|
I stepped down to the following combination: |
|
If you go to window->preferences->erlang->troubleshooting, is the connection to the erlang runtime working? |
|
Sorry, I haven't kept that setup, so can't check. |
|
Recently I made a "least effort" Erlide installation, accepting default offers all the way. The yellow marks work! Version details are xubuntu 20.04.4 |
I am running Eclipse IDE for Java Developers 4.23, and then I have installed Erlang language tools IDE 0.60.4.v20210610-1117.
Maybe these software versions don't play well together. If I create an unused non-exported function for example, it will appear on the Problems listing, but the Location column has "line 0". Also there is no yellow mark in the left margin of the editor window. The same goes for compiler errors: no red marks.
The text was updated successfully, but these errors were encountered: