Note that there are some explanatory texts on larger screens.

plurals
  1. POCLASSPATH set but java compiler cannot find class files
    primarykey
    data
    text
    <p>I am running Ubuntu 11.10 and have installed jdk-6u30-linux-i586.bin and have a directory /usr/local/jdk1.6.0_30 and everything was working and compiling fine even without a CLASSPATH so long as I had export PATH=/usr/local/jdk1.6.0_30/bin:$PATH in my ~/.bashrc and executed java from a fresh new shell (not sure why no CLASSPATH is needed in my env).</p> <p>Now I am trying to use the following class libraries: <a href="http://code.google.com/p/google-api-java-client/downloads/list" rel="nofollow">http://code.google.com/p/google-api-java-client/downloads/list</a> google-api-java-client-1.6.0-beta.zip</p> <p>I downloaded and extracted the zip file to a /usr/local/google directory which now contains all the jar files. I then try to compile the BigQuerySample from <a href="http://code.google.com/p/google-api-java-client/wiki/ClientLogin" rel="nofollow">http://code.google.com/p/google-api-java-client/wiki/ClientLogin</a></p> <p>$ javac -cp /usr/local/google BigQuerySample.java</p> <p>and I get:</p> <p>BigQuerySample.java:1: package com.google.api.client.googleapis does not exist import com.google.api.client.googleapis.*;</p> <p>and so on for all the imported packages except for java.io.*;</p> <p>I know this should be a simple classpath problem but adjusting the classpath on the command line or in the environment with export CLASSPATH=$CLASSPATH:/usr/local/google does not get rid of the errors. I have tried jar -tvf *jar for each jar file and the stuff is there, so why is the java compiler not finding the includes?</p> <p>Thanks,</p> <p>John Goche</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload