Java interface compilation fails about omorfi HOT 5 CLOSED

There's a PR hfst/hfst-optimized-lookup#14... having a config switch for classpath sounds like a good idea, I'll try to get it before next release.

from omorfi.

While waiting for PR hfst/hfst-optimized-lookup#14 to get merged, an interim workaround could be to just fork the repository and do a custom OL release similar to this:
https://github.com/marko-asplund/hfst-optimized-lookup/releases

Otherwise, it can be quite difficult for people to compile Omorfi.

Also, some users might want to skip building the Java interface altogether.

from omorfi.

While waiting for PR hfst/hfst-optimized-lookup#14 to get merged, an interim workaround could be to just fork the repository and do a custom OL release similar to this:
https://github.com/marko-asplund/hfst-optimized-lookup/releases>

Sounds like a good idea, or maybe I'll just include the modified source tree to omorfi while / if the official one doesn't get fixed.

Also, some users might want to skip building the Java interface altogether.

Yeah, that was the original intent and should be resolved by #45 which will be included in the next release.

from omorfi.

👍

from omorfi.

So, current develop branch has optional java (default off), and a bundled hfst. The classpath override may work in --with-java[=classpath].

from omorfi.