Public bug reported:
Since jtreg 5.1-b01-1 it will no longer run without having JTREG_HOME
(or JT_HOME) explicitly set on the environment, previous versions worked
ok.
It will exit 1 when trying to run it:
$ jtreg
Cannot determine JTREG_HOME; please set it explicitly
The reason is a change in debian/patches/launcher.patch that adds the check
if [ -z "${JTREG_HOME}" ]; then
JTREG_HOME="/usr/share/jtreg"
fi
too further down compared to the previous jtreg version. This causes the
code to search for lib/jtreg.jar in the script's path (/usr/bin) first,
which does not work and then calls exit 1.
That check is added exclusively for Debian/Ubuntu by d/p/launcher.patch
and should come before jtreg will try to look for lib/jtreg.jar by
itself.
** Affects: jtreg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887587
Title:
jtreg fails to locate its own lib directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jtreg/+bug/1887587/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
