Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360014 - Misleading error message "AnalysationIssueType not found: <class>"
Summary: Misleading error message "AnalysationIssueType not found: <class>"
Status: CLOSED FIXED
Alias: None
Product: M2T
Classification: Modeling
Component: Xpand (show other bugs)
Version: 1.1.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 trivial (vote)
Target Milestone: M3   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-05 12:50 EDT by Karsten Thoms CLA
Modified: 2013-02-21 08:11 EST (History)
0 users

See Also:
karsten.thoms: juno+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Thoms CLA 2011-10-05 12:50:08 EDT 
The actual message should be "Type not found". This error indicates that Xpand was not able to resolve a specific type.

File to fix: AnalysationIssue.
Also the plugin test SimpleProjectTest#testBug134646 must be adjusted, since it expects a different message.
Comment 1 Karsten Thoms CLA 2011-10-07 01:56:15 EDT 
The actual place to fix was IMarkerFactory$Default. The issue type string was prepended to the actual error message. Without this, the error message is again as before.
Comment 2 Karsten Thoms CLA 2013-02-21 08:11:16 EST 
Bug resolved before Xpand 1.2 release date => Closing