Jing dependencies (java runtime, batik, avalon-framework)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Confirmed
|
Medium
|
Unassigned | ||
jing-trang (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Ubuntu GNOME 16.04.
jing 20131210+dfsg+1-4 (xenial)
java-wrappers 0.1.28 (xenial)
Using jing gives:
[warning] /usr/bin/jing: No java runtime was found
[warning] /usr/bin/jing: Unable to locate avalon-framework in /usr/share/java
[warning] /usr/bin/jing: Unable to locate batik-all in /usr/share/java
I did install some more Java stuff and could get rid of avalon and batik warnings (meaning a dependencies problem in the jing package), but still "No java runtime".
Warning "No java runtime was found" seems to come from java-wrappers.sh in case of problems to find JAVA_HOME.
As a workaround, I did add
JAVA_HOME=
JAVA_CMD=
on lines 2 and 3 of the jing script and commented out find_java_runtime — and jing does not protest any more !
It even works: detects faulty TEI XML (against RelaxNG) and let it pass after correction.
I am not a professional, and know almost nothing about Java. The above was mainly guesswork. Hope this helps.
Changed in jing-trang (Ubuntu): | |
importance: | Undecided → Medium |
Changed in hundredpapercuts: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Thanks for taking your time to report this issue and help making Ubuntu better.
I get the same warnings when running jing 20131210+dfsg+1-5 on Ubuntu Yakkety. /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 834554). That one seems to be a false positive because it first checks for Oracle java, then OpenJDK which could result in this warning. So the java runtime part should be covered.
I did some research and found a Debian bug report which deals with the Java runtime warning (https:/
The upstream bug report doesn't mention the avalon/batik warnings though, so that might be a separate issue. I'm not familiar with this package though, so I don't really know which dependencies it needs. You mentioned it worked, despite(?) the warnings, did it also work before you installed avalon-framework and locate batik-all or did the whole or parts of the program fail? Are there parts of the program which stops working if you uninstall them again. In case they are needed, they should probably be added as dependencies so that they are installed alongside.