Hook for OmegaT translation kit not working anymore

[YvesS]

When creating an OmegaT project using okapi-step-rainbowkit we assume the Rainbow JAR file name is rainbow.jar but now it is named with the version number, so the file is not found and the hook command-line is not created.

We also need to generate at least a warning when the hook cannot be set during the project creation.

See report and discussion here: https://groups.google.com/d/msg/okapi-users/YUFguFor4Ag/452-DrJKCAAJ

[YvesS]

Still an issue after changes done.

From Manuel:

When I create the target documents in OmegaT, the translated XLIFF files appear in the /target folder, but no /done folder is created.
If I use the manifest.mrk file for post-processing, then the done files are created without errors.
So it does help for my immediate purposes, but it seems there's still something not right in the post-processing hook used by OmegaT at compile time.

[Manuel Souto Pico]

Thanks, Yves. For the sake of completeness: Project created with the latest 1.40 snapshot of Okapi and tested in OmegaT versions 4.2.0 and 5.2.0 on Windows 10.