Re: [mdt-ocl.dev] OclInEcore editor behaviour

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi Alex

My editor fixes for RC1 are all in and a Hudson build succeeds.

RoyalAndLoyal.ecore now has 0 errors, since lookups now resolve the template parameterisation of source expressions.

Company.ecore still has errors from lack of integration of additional OCL properties. Hope to fix this for RC2.

IMO by default the priority of the OclInEcore editor should be less than the priority of the standard sample ecore model editor.

Fixed in RC1.

I may commit some Outline customisation in the next 24 hours, so you should pick it up if you do RC1 late in the day.

    All the best

        Ed