I am sending this to the list's address since reportbug keeps failing to deliver reports to debian, don't know why ...

I create my Java-packages from the JDK installer via


When using them with Eclipse and Ant, using "JRE"->"Run in the same JRE as the workspace", Ant fails with the message

com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK.
It is currently set to "/usr/lib/jvm/jdk-7-oracle-x64/jre"

JAVA_HOME is nowhere actively defined, so it must be done by Eclipse internally. Investigating why it points to "/usr/lib/jvm/jdk-7-oracle-x64/jre" instead of "/usr/lib/jvm/jdk-7-oracle-x64" I checked /usr/bin/java:

/usr/bin/java -> /etc/alternatives/java -> /usr/lib/jvm/jdk-7-oracle-x64/jre/bin/java

I am pretty sure, this is the cause -- Eclipse constructs the JAVA_HOME value from this path. Checking update-alternatives, I only se the JRE, despite the JDK being available:

# update-alternatives --config java
There are 2 choices for the alternative java (providing /usr/bin/java).

Selection Path Priority Status
* 0 /usr/lib/jvm/jdk-7-oracle-x64/jre/bin/java 317 auto mode 1 /usr/lib/jvm/jdk-6.43-oracle-x64/jre/bin/java 316 manual mode 2 /usr/lib/jvm/jdk-7-oracle-x64/jre/bin/java 317 manual mode

I'd like to be able to select the JDK, too, at this point. So, java-package/make-jpkg should add that to the alternatives if present in the created deb package.


This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to