Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329740 - Rules implemented in UML2 metamodel cannot be disabled or precisely selected in preferences
Summary: Rules implemented in UML2 metamodel cannot be disabled or precisely selected ...
Status: VERIFIED FIXED
Alias: None
Product: MDT.UML2
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: M6   Edit
Assignee: UML2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-09 04:38 EST by Yann Tanguy CLA
Modified: 2012-03-19 14:02 EDT (History)
3 users (show)

See Also:
Kenn.Hussey: juno+

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 Yann Tanguy CLA 2010-11-09 04:38:06 EST 
It seems that the user has no access to the set of rules to validate (speaking of rules implemented in UML2 metamodel here),
all these rules are always verified.

It would be nice to allow the users to select only a subset (or disable all) of these rules for validation.
Comment 1 Kenn Hussey CLA 2010-11-09 09:09:45 EST 
This is something that would need to be done in a consuming application/project, e.g., by registering the constraints defined in UML2 as "rules" via the EMF Validation project. There is no plan to create a dependency directly between UML2 and EMF Validation.
Comment 2 Kenn Hussey CLA 2011-05-31 10:37:26 EDT 
Closing for Indigo release.
Comment 3 Kenn Hussey CLA 2012-03-19 14:01:53 EDT 
This has actually been resolved in Juno with the introduction of a dynamic provider for UML2 constraints per bug 373643.