|Re: [mdt-ocl.dev] OCL Tools RC4|
Hi Some useful typos cured. Thanks. On 11/06/2013 12:26, Adolfo Sanchez-Barbudo Herrera wrote:
- Java API points to classic programmers guide. I guess that pointing to Pivot one will be made as soon as the code is promoted.
It has taken me a long time to understand why the M1/M2 distinction was there. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=400090.- I don't understand this classic console related phrase: M1/M2The classic Console provides a selection to determine whether the selected metamodel binding is that for objects (M2) or types (M1).
- In the papyrus integration one, I don't understand why you want/need to do the following distinction:Once Papyrus fixes validation display, the metaclass invariants section should have extra text explaining how you can see your constraint failing within the Class Diagram editor.•class invariants to be observed by user models •metaclass invariants to be observed by class diagrams
When the bugzilla is approved I'll start with OCL Tools RC4 build.
Go for it. Regards Ed
Back to the top