| [mdt-ocl.dev] Xtext editor progress |
HiAfter Nick Boldt explained how we were using the wrong build dependencies and Sebastian Zarnekow pointed me at AMP as an each Hudson build to copy, the build now builds the Xtext examples editors. So https://build.eclipse.org/hudson/job/cbi-mdt-ocl-3.0/175/artifact/build/N201004221308/mdt-ocl-Update-N201004221308.zip can be used to fully populate a naked Eclipse installation. Then just do New File ... temp.oclinecore or temp.ocl, and use Ctrl-Space for content assist.
I hope to enhance the editors to have some semantic utility over the weekend; they already resolve Let variables and scopes, but not features. This probably needs addition of an examples.xtext.library editors to support definition of the OCL library so that e.g. forAll is defined. The editors are independent of the code so it is easier to do this than struggle to rescue the existing Ecore/UML definitions.
After some probing it is clear that the Helios build uses the ocl.all feature, which is a non-examples subset of the ocl.master.feature that populates the SDK and Update site. There is therefore no hazard or issue regarding the IP/CQ/Rundown validity of the examples editors in Helios. They are not in Helios, but they should be in the Update sites that should be resolvable from the Amalgam Modeling Discovery UI.
Regards
Ed Willink