Commit 391d80c added a module that simplifies the conversion of WordNet lexicons. It does this by using a hard-coded(!) extJWNL properties file. Unfortunately, this file works only for extJWNL ≤ 1.8.0, whereas at the time UBY used extJWNL 1.9.0 (and now uses 1.9.1). This means that calls to the WordNetCreator() constructor trigger error messages similar to those seen in Issue #120.
A quick fix would be to replace the hard-coded file with one for extJWNL 1.9.1, which I will do shortly. (Ideally, however, this file should not be hard-coded but rather read from a file in src/main/resources and automatically patched for the correct dictionary path. Even more ideally, the UBY could use extJWNL's own version of the WordNet dictionaries, which are now available as Maven artifacts.)
Commit 391d80c added a module that simplifies the conversion of WordNet lexicons. It does this by using a hard-coded(!) extJWNL properties file. Unfortunately, this file works only for extJWNL ≤ 1.8.0, whereas at the time UBY used extJWNL 1.9.0 (and now uses 1.9.1). This means that calls to the WordNetCreator() constructor trigger error messages similar to those seen in Issue #120.
A quick fix would be to replace the hard-coded file with one for extJWNL 1.9.1, which I will do shortly. (Ideally, however, this file should not be hard-coded but rather read from a file in src/main/resources and automatically patched for the correct dictionary path. Even more ideally, the UBY could use extJWNL's own version of the WordNet dictionaries, which are now available as Maven artifacts.)