Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 464015

Summary: Wrong VSM editor property sections orders on Mars
Product: [Modeling] Sirius Reporter: Maxime Porhel <maxime.porhel>
Component: CoreAssignee: Project inbox <sirius.core-inbox>
Status: CLOSED INVALID QA Contact: Pierre-Charles David <pierre-charles.david>
Severity: normal    
Priority: P3 CC: belqassim.djafer, pierre-charles.david
Version: 2.0.0Keywords: triaged
Target Milestone: 3.0.0M7   
Hardware: PC   
OS: Mac OS X   
Whiteboard:
Bug Depends on:    
Bug Blocks: 456318    
Attachments:
Description Flags
Container mapping property sections order on Mars none

Description Maxime Porhel CLA 2015-04-07 05:47:58 EDT
Created attachment 252191 [details]
Container mapping property sections order on Mars

Steps to reproduce: 
 . Create a VSM in Mars
 . Create a Viewpoint, a diagram, and a container mapping
 . The sections are not in the expected order (See Sirius releases of 1.0.x or 2.0.x on luna)






I have the issue on Mac OS with Mars M6 and Sirius master. 
The issue does not appear on Laurent's pc (Linux, Luna target, Sirius master)

All property section orders will have to be checked
Comment 1 Belqassim Djafer CLA 2015-04-08 05:46:29 EDT
I do not have this problem (Windows 8.1, Mars, Sirius 3.0.0M6 and Sirius Nightly)
Comment 2 Belqassim Djafer CLA 2015-04-16 09:53:50 EDT
After making changes in PropertySection, the VSM editor property sections order changed on container mapping.
And I reproduced this issue on Windows 8 with Mars and Luna target platform and Sirius master.
Comment 3 Belqassim Djafer CLA 2015-04-16 10:40:53 EDT
After several Eclipse restarts and target platform changes, the order became normal in the same configuration described in the Comment 2 !
Comment 4 Pierre-Charles David CLA 2015-04-22 03:36:11 EDT
It looks like this could be caused by launching an Eclipse runtime from a dev environment where the property sections have been re-generated (with the wrong order defined in the plugin.xml). Once this has been done once, even reverting the plugin.xml in the dev env and relaunching does not fix the issue, maybe because of some caching of registry entries performed in Mars?

More tests are needed to confirm, but if this is the explanation, this can not happen in production so we can probably close it (and maybe open a but on platform or PDE if there is some caching issue there).
Comment 5 Maxime Porhel CLA 2015-04-27 10:59:29 EDT
I confirm Pierre-Charles's comment: after holidays, runtime workspace clean up, branch switch (with no effect on the section order), I do not reproduce the issue anymore. And I made some editor regeneration before seeing the issue.
Comment 6 Pierre-Charles David CLA 2015-05-21 10:50:22 EDT
I checked again on a few types in the VSM editor, and everything looks fine.

Verified on Sirius 3.0.0rc1a.
Comment 7 Pierre-Charles David CLA 2015-06-24 11:20:00 EDT
Available in Sirius 3.0.0. See https://wiki.eclipse.org/Sirius/3.0.0.