| Summary: | UMLNavigator...Providers: code generated with 3.6RC shuffles elements in switch structures | ||
|---|---|---|---|
| Product: | [Modeling] GMF-Tooling | Reporter: | Elena Shaverdova <eshaverdova> |
| Component: | Samples | Assignee: | Elena Shaverdova <eshaverdova> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | borlander, eshaverdova |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Generation diff on navigator providers commited as sigle commit. |
Build Identifier: I20100513-1500 After regeneration with GMF for 3.6RC, all UMLNavigatorLabelProviders and UMLNavigatorLabelProviders contain large structures like this code snippet: switch (UMLVisualIDRegistry.getVisualID(view)) { case PackageEditPart.VISUAL_ID: return ...; case ActivityEditPart.VISUAL_ID: return ...; case ... new code shuffles cases, it creates a huge diff for regeneration, without adding any meaningful differences. => Either force processed elements to have the same order as before, or commit the big generation diff in single commit (once) which does not include any other changes. Reproducible: Always