Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365969 - Eclipse freezes when EPackage.name is null or empty
Summary: Eclipse freezes when EPackage.name is null or empty
Status: CLOSED FIXED
Alias: None
Product: EMFCompare
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: EMF Compare CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-07 16:52 EST by Gregor Bonifer CLA
Modified: 2011-12-12 04:43 EST (History)
2 users (show)

See Also:

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 Gregor Bonifer CLA 2011-12-07 16:52:03 EST 
Eclipse freezes when the compared models contain an EPackage whose name attribute is an empty string or null. This only occures when only the selected resources and not their resourcesets are compared.

The bug can be reproduced with the following steps: 
- *Make sure all your work is saved!*
- Create two ecore-files via the New Ecore File wizard.
- Mark both files and select Compare With > Each Other from the context menu.
- Choose "Selected resource(s) only"

Regards,
Gregor
Comment 1 Laurent Goubet CLA 2011-12-12 04:43:44 EST 
This was a really well hidden infinite loop deep inside the UI code. It has now been fixed on master and will be available in tomorrow's M4 build. (This will also find its way in the maintenance stream.)