-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration.tableauMonitorType is final?? #11
Comments
Hi, version 1.3.8.413 (and all versions released under the In that repo the field is final - not sure off the top of my head why. |
Thank you, @ignazio1977. Yes, I see it, and at least now I know I'm not going crazy. |
Version 1.4.5.456 is OWLAPI 4 compatible and includes a fix for this. You should be able to add it as dependency and it should override 1.3.8.413. If not, you might need to exclude it explicitly. Haven't tried it with Tawny OWL, but in theory it should be a drop in replacement. |
Hi @ignazio1977: Yes, thank you! That worked perfectly. :) In case anyone else has a similar issue, here is what needs to go into (defproject ...
...
:dependencies [...
...
[net.sourceforge.owlapi/org.semanticweb.hermit "1.4.5.456"] ; Override Tawny's dep
[uk.org.russet/tawny-owl "2.0.0"]
...]) |
Hello,
In version 1.3.8.413 of HermiT (pulled in via Tawny-OWL 2.0.0) I am unable to set
Configuration.tableauMonitorType
. Java reports that the class member is final; however on githubConfiguration.java
does not show the field as final (not even in the file's history), and theHermiTConfigurations.java
example is setting it toTableauMonitorType.TIMING
, which is what I want to do.I am ultimately trying to get this working in Clojure:
However, for sanity's sake, I created some test code in Java:
Alas, it won't compile for the same reason.
I have tried setting a number of other fields in the Configuration object from Clojure, and it all works fine. This problem has baffled me because the HermiT source code does not show
tableauMonitorType
as final. I see now in issue #6 that this is not the official repository, so perhaps version 1.3.8.413 was created from a slightly different source tree. Can you suggest a work-around?Thank you,
den Drown
The text was updated successfully, but these errors were encountered: