On Fri, 15 Aug 2008 17:22:14 -0000, Launchpad Bug Tracker wrote:
[Disclaimer: I'm the maintainer of JabRef in Debian. I'm not
responsible for the package in Ubutnu, but the wrapper script you are
referring to is from me.]
> The JabRef package selects the JavaVM itself:
[..]
> test -n "$JAVA_HOME" && JAVA=${JAVA_HOME}/jre/bin/java
> fi
>
> export JAVA=${JAVA:=java}
>
> exec $JAVA -cp
> /usr/share/java/jabref.jar:/usr/share/java/antlr.jar:/usr/share/java/antlr3.jar:/usr/share/java/looks.jar:/usr/share/java/forms.jar:/usr/share/java/spin.jar:/usr/share/java/glazedlists.jar:/usr/share/java/microba.jar:/usr/share/java/pdfbox.jar:/usr/share/java/jempbox.jar
> net.sf.jabref.JabRefMain "$@"
[..9
> I expected it to pick the VM I've selected with update-java-alternatives.
You can us it with other JVMs if you set $JAVA_HOME.
The reason for the decision to look for specific Java VMs is
(1) in my experience JabRef only works with sun-java and openjdk
(2) I've received a couple of bug reports before I changed the wrapper
scripts, which where caused by having the alternatives system
point to some other JVM, and I got a bit tired of explaining
to all of the bug reporters that they have to choose sun-java via
update-alternatives.
In the Debian BTS I would take this bug "wontfix" but I leave the
manipulation of the bug in Launchpad to the Ubuntu guys.
Cheers,
gregor
--
.''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4
: :' : debian gnu/linux user, admin & developer - http://www.debian.org/
`. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/
`- BOFH excuse #421: Domain controller not responding
--
jabref doesn't start with my JavaVM of choice
https://bugs.launchpad.net/bugs/258198
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
