Rainbow command-line mode won't run on machines without a display

[Chase Tingley]

See thread.

Julian is running Rainbow in batch mode on a machine with no display. This appears to be impossible, because Rainbow tries to get a UI handle and fails.

julien@ubuntuSERVER:~/okapi/lib$ java -jar rainbow.jar -x TranslationKitCreation /home/julien/test.html -o /home/julien/test/xliff
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.widgets.Display.createDisplay(Unknown Source)
        at org.eclipse.swt.widgets.Display.create(Unknown Source)
        at org.eclipse.swt.graphics.Device.<init>(Unknown Source)
        at org.eclipse.swt.widgets.Display.<init>(Unknown Source)
        at org.eclipse.swt.widgets.Display.<init>(Unknown Source)
        at net.sf.okapi.applications.rainbow.Main.main(Main.java:33)

When running with -x or -pln, we should see if we can defer initializing SWT until we know we need it.

[Chase Tingley]

Upgrading to critical because this blocks CI builds in gitlab.

[Mihai Nita]

Fixed and enabled application integration tests run in CI.

• Commit: https://bitbucket.org/okapiframework/okapi/commits/1681bb48df01dec15120ca7d179dd0a4dbb3266
• CI run: https://gitlab.com/okapiframework/okapi/pipelines/56675455

[Chase Tingley]

Wow, thank you!