Bug 517000 - Improve error reporting in VSM validation when typename can not be found
Summary: Improve error reporting in VSM validation when typename can not be found
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard: vsm validation
Keywords: helpwanted, triaged
Depends on:
Blocks:
 
Reported: 2017-05-19 11:59 EDT by Laurent Redor CLA
Modified: 2017-06-12 08:14 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Laurent Redor CLA 2017-05-19 11:59:00 EDT 
While validation of bug 510692, I observed that validation concerning typename can be improved.
Since the bug 510692, if the reference typename has not its dependency to the metamodel, a warning is logged during validation "The EClass uml::Class used in domainClass is not accessible. You are most likely trying to use an EClass without having a dependency to its plugin.".
But if the class in not accessible, not present in the target platform, there is also an error logged "The Class uml::Class does not exist.". This check is done in org.eclipse.sirius.diagram.tools.internal.validation.description.constraints.ExistingDomainClassConstraint.

The message of these 2 checks must be improved to explain more clearly what the user needs to fix them. Or maybe the first message (the warning) must no be logged if we are in the second context.
Comment 1 Pierre-Charles David CLA 2017-06-12 08:14:43 EDT 
Agreed