#139 closed defect (fixed)
Prover not started when run from Product
| Reported by: | Graham Dutton | Owned by: | Graham Dutton |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | 1:pg-eclipse | Keywords: | |
| Cc: |
Description
Prover does not start when run from a Product configuration, though it starts successfully as a plugin. Exception seems to be generated by the system path management which calls the prover and its tools.
Change History (3)
comment:1 Changed 17 years ago by
| Owner: | changed from David Aspinall to Graham Dutton |
|---|
comment:2 Changed 17 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixes in PathUtils? (init was not being called) followed by enhancements to the class, sorted this problem. Prover is now started, but only when a new script is created (by design?). Bugs in project creation seem to hinder the process when packaged as a product.
Note: See
TracTickets for help on using
tickets.
no idea why things are assigned to da by default; perhaps they should be assigned to the reported?