Re: Missing .jinfo files (Was: Re: Switching between different JDK implementations (Debian alternative system & Java))

Holger Rauch wrote: > But invoking "update-java-alternatives -l" as root gives me: > > awk: cmd. line:1: fatal: cannot open file /usr/lib/jvm/*.jinfo' for reading > (No such file or directory) > > The directry "jvm" doesn't exist at all in /usr/lib. Where do those .jinfo > files come from? > > I

Missing .jinfo files (Was: Re: Switching between different JDK implementations (Debian alternative system & Java))

Hi Tom, thanks for your quick reply! But invoking "update-java-alternatives -l" as root gives me: awk: cmd. line:1: fatal: cannot open file /usr/lib/jvm/*.jinfo' for reading (No such file or directory) The directry "jvm" doesn't exist at all in /usr/lib. Where do those .jinfo files come from?

Switching between different JDK implementations (Debian alternative system & Java)

Hi! When wanting to switch between different JDK implementations on Debian, it seems to me one has to use "update-alternatives --config" for each individual binary that's in a JDK. That's sort of awkward. Is there really no wrapper script that I can pass the vendor and/or version no. to and that s

Re: Switching between different JDK implementations (Debian alternative system & Java)

Holger Rauch wrote: > When wanting to switch between different JDK implementations on Debian, it > seems to me one has to use "update-alternatives --config" for each > individual binary that's in a JDK. That's sort of awkward. Is there really > no wrapper script that I can pass the vendor and/or ve