Thanks a lot for your reply. I'll build them locally.
Just one other question hijacking this thread, Eclipse OCL has at least two different "modes":
IIUC, OCLinEcore works only, if im able to manipulate the target Ecore model, right? If im receiving the target Ecore frequently with changes and Im not able to make changes upstream, I need to go for the second approach, as the OCL integration is done outside the Ecore model?
I strongly recommend that you at least skim the OCL documentation to understand the difference between
Classic Eclipse OCL (very stable, not that different to EMF OCL). Some evolution such as selectByKind has been backported.
Pivot/Unified Eclipse OCL (evolving, extensible, modeled, prototype solving may of the major OCL problems)
Most UI functionality uses the Pivot OCL and Xtext. OCLinEcore is a UI for Ecore with embedded OCL, the editor uses Pivot OCL, however you can choose in the OCL preferences whether subsequent execution uses Pivot or LPG/Classic. If you choose to code generate your embedded OCL directly to embedded Java then this uses the Pivot OCL.
If you only want to use Eclipse OCL, just install using Window->Install New Software...
If you want to extend Eclipse OCL you must decide whether stable bugs or evolving fixes are better suited to you usage.