Execution backends should be possible to start without launch configuration
This is probably only the case when debugging Erlide itself, we start the second instance as an Eclipse launch.
We must be able to register the backends as an execution backend for the erlide projects.
We must be able to register the backends as an execution backend for the erlide projects.
Leave a comment
on 2008-08-20 13:06 *
By Vlad Dumitrescu
(Comment removed)
on 2008-08-20 13:06 *
By Vlad Dumitrescu
Priority changed from Normal (3) to High (2)
Priority changed from Normal (3) to High (2)
on 2008-08-27 11:20 *
By Vlad Dumitrescu
Description changed from This is probably only the c... to This is probably only the c...
Milestone changed from 0.4 to 0.5
Description changed from This is probably only the c... to This is probably only the c...
Milestone changed from 0.4 to 0.5
on 2008-08-27 23:41 *
By Vlad Dumitrescu
Summary changed from Execution backends may be started without Erlide launch configuration to Execution backends should be possible to start without launch configuration
Summary changed from Execution backends may be started without Erlide launch configuration to Execution backends should be possible to start without launch configuration
on 2009-04-09 11:45 *
By Vlad Dumitrescu
Milestone changed from backlog to 1.0
Milestone changed from backlog to 1.0
Updating tickets (#133, #134, #40, #55, #79, #98, #113, #114, #120, #125, #129, #131, #137, #147, #157, #176, #177, #179, #204, #211, #222, #228, #256, #323, #325, #41, #45, #46, #52, #57, #61, #64, #76, #83, #93, #95, #100, #111, #115, #119, #130, #135, #145, #148, #149, #150, #152, #155, #156, #159, #163, #164, #168, #170, #172, #173, #181, #182)
Updating tickets (#147, #349, #79, #137, #157, #204, #80, #242, #401, #359, #366, #373, #364, #377, #76, #168, #170, #241, #245, #252, #276, #317, #339, #351, #372, #374, #380, #405, #58, #89, #116, #121, #169, #174, #175, #188, #205, #223, #240, #340, #354, #166, #56, #106, #277, #328, #53, #84, #99, #216, #237, #247, #249, #314, #321, #403)
on 2009-07-17 01:22 *
By Vlad Dumitrescu
Status changed from New to Fixed
Work remaining changed from 40.0 to -none-
Status changed from New to Fixed
Work remaining changed from 40.0 to -none-
this is fixed with selfhost plugin