Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] Rename and Micro-Versions


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

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.



Back to the top