Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313880 - [Usability] No warning during/after opening a model, if applied profiles are not installed
Summary: [Usability] No warning during/after opening a model, if applied profiles are ...
Status: CLOSED FIXED
Alias: None
Product: MoDisco
Classification: Modeling
Component: Infrastructure (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: 0.9.0 M3   Edit
Assignee: Nicolas Bros CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 320095
Blocks:
  Show dependency tree
 
Reported: 2010-05-21 04:35 EDT by Ansgar Radermacher CLA
Modified: 2011-04-28 10:47 EDT (History)
4 users (show)

See Also:
nicolas.bros: indigo+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ansgar Radermacher CLA 2010-05-21 04:35:02 EDT
Build Identifier: Build id: 20100506-2000

If a model using one or more profiles that are not installed is openend, a warning shows up in error log. There is however no warning e.g. in form of an information dialog which informs the user about this problem.
Many users might thus be unaware about the installation problem (and simply do not see profile and stereotype applications that are actually there) since they do not open and/or consult the error-log by default.


Reproducible: Always
Comment 1 Nicolas Bros CLA 2010-07-16 08:14:07 EDT
I tried to create a profile to reproduce, but I couldn't apply it (see Bug 320095).
Comment 2 Gregoire Dupe CLA 2010-10-06 09:58:18 EDT
Moving to P2: A pop-up message could be useful to inform the user when a referred model cannot be resolved.
Comment 3 Nicolas Bros CLA 2010-10-08 10:10:23 EDT
In revision 3306, I added a button that appears in the browser when errors or warnings are found on the Resource. When this button is clicked, it opens a dialog that displays all errors with their associated message.

A missing profile will not be detected immediately when the Resource is opened, because the Resource it references is lazy loaded, and the error will appear only when trying to access an element in this Resource.
Comment 4 Hugo Bruneliere CLA 2010-10-21 05:09:08 EDT
The bug has been fixed in latest revisions.