Open eclipse-ocl-bot opened 1 month ago
By Ed Willink on Sep 07, 2015 05:31
Problem is that the extra guard was added prior to the 'single' call to
UMLOCLEValidator.validateInstanceSpecification
rather than in validateInstanceSpecification itself.
Papyrus' OCLEValidatorAdapter has another call and so bypasses the guard.
Simple fix, move the guard inside validateInstanceSpecification for Neon.
?? for Mars.1
By Ed Willink on Sep 07, 2015 07:04
commit d84e4a7a0b610a62e49a8254beabcebbce568bbb pushed to master for M2
| --- | --- | | Bugzilla Link | 476759 | | Status | NEW | | Importance | P3 normal | | Reported | Sep 07, 2015 04:20 EDT | | Modified | Oct 29, 2015 08:41 EDT | | Reporter | Ed Willink |
Description
Mars.1RC2: The attachment to Bug 476662 demonstrates a Papyrus validation failure that should not occur without the OCLforUML stereotype being applied.
OCL->Validate within the UML Model Editor observes the sterotype setting.
However since this is in Mars, maybe we need to delay till Neon to enforce the OCLforUNL profile.