Bug 516903 - Validation should use target platform
Summary: Validation should use target platform
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 4.1.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard: vsm validation
Keywords: triaged
: 516904 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-05-18 11:51 EDT by Melanie Bats CLA
Modified: 2017-06-16 04:32 EDT (History)
2 users (show)

See Also:


Attachments
Test project (5.91 KB, application/zip)
2017-05-18 11:51 EDT, Melanie Bats CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Melanie Bats CLA 2017-05-18 11:51:25 EDT
Created attachment 268448 [details]
Test project

When I create a odesign which references an icon which is defined inb a dependent plugin, even if this plugin is defined as a required bundle and is available in the target platform, Sirius generates a validation issue.
To reproduce use the attached project.
Comment 1 Cedric Brun CLA 2017-05-18 12:07:56 EDT
Please note that if the Validation use the target platform to check the image exists, then when directly using the .odesign from the same workspace the runtime should also get the picture out of the target platform and not from the Eclipse host.
Comment 2 Pierre-Charles David CLA 2017-06-13 02:28:01 EDT
*** Bug 516904 has been marked as a duplicate of this bug. ***
Comment 3 Pierre-Charles David CLA 2017-06-16 04:32:05 EDT
Actually, if we start validating image paths according to the current target platform, we should be consistent and validate/use the target platform for all other aspects of the VSM being developed, including metamodels (bugs #471537 and #493331), service completion/validation/execution for all supported languages, and maybe other aspects. Not saying it's a bad idea, on the contrary, just that doing this properly is a significant endeavor.