Opened 17 years ago
Last modified 11 years ago
#64 new task
Decide what to do with ProverStandalone — at Version 2
Reported by: | Owned by: | alexh | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | 1:pg-eclipse | Keywords: | |
Cc: |
Description (last modified by )
Should this code be retained or discarded? Not clear how it fits into future development plans, and already changes elsewhere in code have likely broken it. One possibility may be to move it to another plugin.
In the longer term, we've talked about adding an API to the Broker to manage running provers, so the code here would form a basis for that.
Change History (2)
comment:1 Changed 17 years ago by
Milestone: | PG-Eclipse-1.0.6 → PG-Eclipse-1.0.7 |
---|---|
Summary: | Decide what to do with !ProverStandalone → Decide what to do with ProverStandalone |
comment:2 Changed 17 years ago by
Description: | modified (diff) |
---|---|
Owner: | changed from David Aspinall to alexh |
Note: See
TracTickets for help on using
tickets.