Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315274 - UMLNavigator...Providers: code generated with 3.6RC shuffles elements in switch structures
Summary: UMLNavigator...Providers: code generated with 3.6RC shuffles elements in swit...
Status: RESOLVED FIXED
Alias: None
Product: GMF-Tooling
Classification: Modeling
Component: Samples (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Elena Shaverdova CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-01 14:47 EDT by Elena Shaverdova CLA
Modified: 2012-12-11 15:12 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elena Shaverdova CLA 2010-06-01 14:47:55 EDT
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
Comment 1 Elena Shaverdova CLA 2010-06-07 06:29:09 EDT
Generation diff on navigator providers commited as sigle commit.