You are not logged in.
I have had an issue where starting protégé on terminal would print several error messages accusing some missing dependencies:
Error starting file:/usr/share/java/protege/bundles/protege-common.jar
org.osgi.framework.BundleException: Unable to resolve org.protege.common [1](R 1.0): missing requirement [org.protege.common [1](R 1.0)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j)(version>=1.7.0)(!(version>=2.0.0))) [caused by: Unable to resolve slf4j.api [17](R 17.0): missing requirement [slf4j.api [17](R 17.0)] osgi.ee; (&(osgi.ee=JavaSE)(version=1.5.0))] Unresolved requirements: [[org.protege.common [1](R 1.0)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j)(version>=1.7.0)(!(version>=2.0.0)))]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111) ~[org.apache.felix.main.jar:na]
at org.apache.felix.framework.Felix.startBundle(Felix.java:2117) ~[org.apache.felix.main.jar:na]
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371) ~[org.apache.felix.main.jar:na]
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308) ~[org.apache.felix.main.jar:na]
at java.base/java.lang.Thread.run(Thread.java:829) ~[na:na]
After finding this issue I was convinced I had to downgrade the java running in my environment to jre 8.
Reading the docs, I came accross the convenient helper archlinux-java that changes the version which java points to. Running
sudo archlinux-java set java-8-openjdk/jre
solved my problem.
My question now is, is there anything I can do to document this so that other users running into this issue might find this solution easier, without having to work out the reason why their installation is failing?
Last edited by gchamon (2021-05-24 10:32:34)
Offline
Adding a page for protege on the archlinux wiki is a possibility.
The dependencies on https://archlinux.org/packages/community/any/protege/ are satisified if only jre11-openjdk is present .
Were you running that java version when those errors came ?
If that's true then the dependencies may be incorrect .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Were you running that java version when those errors came ?
If that's true then the dependencies may be incorrect .
Exactly. Actually, now that I come to think of it, the first time it didn't even launch, because java was a broken symlink. Installing java-runtime-common fixed the broken link, but the program began complaining about unresolved dependencies.
After installing jre8-openjdk and running archlinux-java to change my environment to point to java 8, the program started normally.
Is there any way I can suggest a change to the package dependencies?
EDIT
Maybe the bug report link on the page?
Last edited by gchamon (2021-05-24 10:55:49)
Offline
I'm inclined to say a Bug Report is warranted , but have been wrong about that before.
For now I suggest to wait a while (like 24 hours ) for other posters.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline