[mdt-ocl.dev] Rename and Micro-Versions

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

https://bugs.eclipse.org/bugs/show_bug.cgi?id=420431

demonstrates some pain caused by installing incompatible OCL and QVTd 
versions (the CS rename was inconsistent).

I think we can avoid this happening again for derived projects, by 
requiring that every API rename causes a 0.0.1 increment in 
org.eclipse.ocl.examples.domain. Tightly coupled projects can then 
specify an exact match on this version.

NB. Your 'AbstractPackageCS' might be the first of these, since it 
requires re-auto-generation of XXXSwitch.java.

Within the OCL GIT, renames can affect quite a few files, so it is 
probably prudent to give a couple of days notice of the rename to allow 
as many active branches as possible to be shutdown to avoid rename 
concurrency.

    Regards

        Ed