Bugzilla – Full Text Bug Listing
| Summary: | Error Messages when Extensions are broken | ||
|---|---|---|---|
| Product: | [Modeling] M2T | Reporter: | Markus Voelter <voelter> |
| Component: | Xpand | Assignee: | Karsten Thoms <karsten.thoms> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | karsten.thoms, sebastian.zarnekow, sven.efftinge |
| Version: | unspecified | Flags: | sven.efftinge:
helios+
|
| Target Milestone: | M5 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 292770 | ||
ExecutionContextImpl#internalAllExtensions() threw a RuntimeException when an extension file cannot be parsed. As a result when one extension file is broken, all extensions cannot be found. Processing must continue dispite of the broken extension file. I think this annoying problem is now fixed. Also content assist is now working again :-) Bug resolved before Xpand 1.2 release date => Closing |
If an extension file imports another one, or if a template imports and extension and there's something wrong with that extension, I always get the following message: Error Parsing Extensions: null This error message does not tell me anything, and it is shown independent of what the actual problem is. In the 5.x release, we need to make sure that we report error messages that actually specify what the problem is (e.g. "duplicate definition of extension X").