Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 432479 - Prevent profile-update dialog for users models
Summary: Prevent profile-update dialog for users models
Status: VERIFIED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 431953
Blocks: 436666
  Show dependency tree
 
Reported: 2014-04-10 01:44 EDT by Toni Siljamäki CLA
Modified: 2015-01-29 15:42 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Toni Siljamäki CLA 2014-04-10 01:44:13 EDT

    
Comment 1 Toni Siljamäki CLA 2014-04-10 01:47:13 EDT
Copy of comment 11 of Bug 431953:

(In reply to Christian W. Damus from comment #11)
> (In reply to Toni Siljamäki from comment #10)
> > 
> > QUESTION: If a backwards compatible version of a profile is deployed,
> > couldn't user models automatically and safely get updated in the background
> > when the model is loaded, and users only get an "update completed" message
> > to confirm with an advice to save the model if the update was successful?
> 
> I would suggest adding a "Don't ask again for this profile" button to the
> dialog, which would then enable automatic updates for that profile only.
> 
> Please open a new bugzilla for this enhancement.
> 
> 
> > Right after the profile update your new clean-up function can be run and
> > pop-up this new dialog if shit happened as a result of the profile update.
> > (?)
> 
> The implementation in progress would, as it happens, always run before the
> profile update (I think; I need to verify that). But it doesn't matter,
> because profile update does not lead to zombie stereotypes (unless they are
> in resources that are not loaded, but then the repair agent wouldn't see
> those, either).
Comment 2 Toni Siljamäki CLA 2014-04-10 14:36:50 EDT
Copy of Comment 12 of Bug 431953:

(In reply to Toni Siljamäki from comment #12)
> Bug 432479 opened on your request.
> 
> In the case of a profile update, any unpredictable / weird thing can happen,
> like if there are profiles applied to profiles applied to ..., and special
> consideration to Ronans Comment 1 above, depending on existing bugs in
> Papyrus,
> or newly created bugs related to release of new Papyrus functions, etc.
> 
> My point is:
> 
> If this scanning & checking always is run before profile update,
> which I think it should, and there is a profile update right after,
> this scanning & checking must be run again after the profile update.
> 
> ...since things may happen anytime in Papurus rutime, and we need to be
> sure that the model is consistent after any profile update.
> 
> Ronan: Can you provide some additional wisdom here?
Comment 3 Toni Siljamäki CLA 2015-01-29 15:41:52 EST
I'm closing this one, as the Stereotype Repair now works. :)