Bug 481836 - BorderSizeComputationExpression migration is done only on top level containers mapping
Summary: BorderSizeComputationExpression migration is done only on top level container...
Status: CLOSED FIXED
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 3.1.0   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: 4.0.0M4   Edit
Assignee: Maxime Porhel CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on: 465211 481119
Blocks:
  Show dependency tree
 
Reported: 2015-11-10 08:28 EST by Maxime Porhel CLA
Modified: 2016-06-24 08:02 EDT (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 Maxime Porhel CLA 2015-11-10 08:28:13 EST
+++ This bug was initially created as a clone of Bug #481119 +++

BorderSizeComputionExpression migration is done only on top level containers mapping

Steps to reproduce
 * Open an odesign that have at least one container mapping contained into another container mapping made with Sirius 3.0.0 with a Sirius 3.1.0
 * Do a modification in order to save the migrated odesign.
 * Check the style of the container mapping contained into another container mapping
 * See that Border Size Computation is 0 but it should be 1 because 0 means no border since Sirius 3.1.0
Comment 1 Eclipse Genie CLA 2015-11-12 05:46:44 EST
New Gerrit change created: https://git.eclipse.org/r/60191
Comment 2 Eclipse Genie CLA 2015-11-12 11:12:36 EST
New Gerrit change created: https://git.eclipse.org/r/60236
Comment 3 Eclipse Genie CLA 2015-11-13 05:51:39 EST
New Gerrit change created: https://git.eclipse.org/r/60305
Comment 6 Maxime Porhel CLA 2015-11-13 10:09:05 EST
Corrected on master for 4.0.0 M4
Comment 7 Florian Barbin CLA 2016-05-20 08:43:06 EDT
Verified using the junit use case.
Comment 8 Pierre-Charles David CLA 2016-06-24 08:02:19 EDT
Available in Sirius 4.0.0.