Bugzilla – Full Text Bug Listing
| Summary: | Validation should use target platform | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Sirius | Reporter: | Melanie Bats <melanie.bats> | ||||
| Component: | Core | Assignee: | Project inbox <sirius.core-inbox> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cedric.brun, pierre-charles.david | ||||
| Version: | 4.1.1 | Keywords: | triaged | ||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | vsm validation | ||||||
| Attachments: |
|
||||||
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. *** Bug 516904 has been marked as a duplicate of this bug. *** 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. |
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.