| Summary: | Failures in OTTypeHierarchyTests | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] Objectteams | Reporter: | Stephan Herrmann <stephan.herrmann> | ||||
| Component: | OTDT | Assignee: | Stephan Herrmann <stephan.herrmann> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 2.0 | ||||||
| Target Milestone: | 2.1 M3 | ||||||
| Hardware: | Other | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Stephan Herrmann
Created attachment 206073 [details]
fix
This check in HierarchyResolver was too narrow, thus no OTType was
registered for phantom role T7.R1.
Inspecting the file history showed that this change was introduced way back
during the migration to Eclipse 3.2 to accommodate changed processing
order in 3.2, but the condition in question was not further documented.
Released for 2.1 M3 (r2074). The fix has been backported to 2.0.2 via commit 8ad00e64e1caa6f90336b7a9594f5694c29ac893 Tests are green, considering as fixed indeed. |