[ALOY-278] Improve general compile time logging and error output
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-09-19T10:05:26.000+0000 |
| Affected Version/s | 2012 Sprint 19 |
| Fix Version/s | 2012 Sprint 19, Release 3.0.0 |
| Components | XML |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-09-18T06:37:38.000+0000 |
| Updated | 2018-03-07T22:25:47.000+0000 |
Description
ALOY-271 covers errors from the the AST parser, but we need to step through every part of the Alloy process and make sure that all output messages are meaningful and actionable. Validation should explain what exactly failed, not just a "compile failed" message.
Major improvement on compile logging output. There's still work that can be done, but I will create future tickets if they work is started.