Can't Import netscape.javascript; classpath set properly

Question

I have an applet that is trying to say
import netscape.javascript.*No matter how I try to compile it, I get the error
package netscape.javascript does not existI am primarily using ant for building; here is the pertinent section of my build.xml file:
<property name="output" location="javaclasses" />
   <target name="compile">
      <javac srcdir="./"
             destdir="${output}"
             includes="**/*.java"
             classpath="./,\
                        javaclasses/packages/epsgraphics.jar,\
                        /usr/lib/jvm/java-1.5.0-sun-1.5.0_update13-sr2/jre/lib/plugin.jar,\
                        javaclasses"
             listfiles="yes">
      </javac>
   </target>Note that plugin.jar is included in my classpath. Using jar -tf <...>/plugin.jar, I can see that it contains the netscape package, the javascript subdirectory, and the JSObject.class I am interested in.
Attempting to resolve this manually with the command line
javac -classpath "./;javaclasses/packages/epsgraphics.jar;/usr/lib/jvm/java-1.5.0-sun-1.5.0_update13-sr2/jre/lib/plugin.jar;javaclasses" myApplet.javagives the same error.
Moving plugin.jar to my local directory, or any other directory specified in the classpath (which worked just fine until I tried accessing plugin.jar) and re-jiggering the classpath so it can be located gives the same result: it can't find netscape.javascript.
I'm using javac from java-1.5.0-sun-1.5.0_update13-sr2 on Suse Linux 10.3.
What am I missing here?

Answer 1

As noted, the class is present in the jar file, as revealed with 'jar -tf plugin.jar'
I've fiddled with separators, as well. You're correct that a colon is used under Linux; that is what I had used in earlier attempts, but wound up copying the latest incarnation, which was desperately cribbed from another forum's example, thinking that Java might have other ideas. None of the variants I tried worked.
Trying it again, replacing the command line given with colons, still doesn't work; fails with the same message.
Currently pursuing another Ant solution, with no joy.
Thanks for your reply.