What we call a backend is an Erlang runtime that we're connected to via an internal Java node. This connection requires some erlIDE code to be installed and running on the Erlang side.
There are two kinds of backends: managed and standalone. Managed ones have their lifecycle controlled by erlIDE. Standalone ones use already started runtimes.
Inside erlIDE, backends are used for several purposes:
- for the IDE internals: scanning, parsing, etc. This is always a managed backend.
- for compiling code
- for running and debugging the applications
Posts
5 comments:
The weird thing is that if Erlang runtime is broken or misconfigured you can not even get to Preferences page in Eclipse, it just hangs.
@timanovsky: Thanks for the info! We are only testing with a working or a non-existing runtime, didn't consider the case of an existing but non-functional one. I will add an issue on this.
Fixed! Now we only try to restart a crashed runtime once. Fix will be available in the next build.
Vlad, thank you for fixing this so fast! Very good product I use in my everyday work.
You're welcome. If there's anything more that isn't as it should, please let me know directly. However, there's no guarantee that the fix will come as fast as today's :-)
Post a Comment