How is that going to be configured?

A simple option is to provide a couple of preconfigured LCs, with some sane defaults. Actually, we can't know how the user configuration looks like, so these LCs will have to be adjusted at startup, filling in the runtime info, letting all projects be included and so on. We have to listen for resource changes, to catch projects that are created.

Simple is the keyword here: the point is not to provide for every possible thing, the point is to have a way to create an erlang program and run it within eclipse. A quick-launch that creates or reuses a launch config with the selected project(s) and some reasonable settings is probably enough.

Updating tickets (#156, #550, #554, #649, #650, #606, #631, #755, #782, #783, #714, #747, #753, #688, #712, #723, #730, #732, #733, #734, #735, #740, #756, #757, #758, #763, #764, #765, #777, #787, #792, #689)

Updating tickets (#723, #730, #732, #733, #734, #735, #740, #753, #755, #756, #757, #764, #782, #787)