> Maybe I'm not so quick about this, but I can't seem to figure out how one > gets JDE to compile a program that's in a package, correctly w/o forcing a > -classpath in the compile time options? I don't know what you mean by this. JDE does not care if the java file is in a package or not. In order to compile the compiler (javac, jikes, etc...) needs to be able to find the java file. In javac if you don't want to pass the -classpath argument the $CLASSPATH environment variable needs to be set. Instead of that you can set the JDE variable jde-global-classpath.
> > why is this? > > I am trying to edit > > proj3.controller.MyController.java > > so I call emacs proj3/controller/MyController.java > > the file has the package line appropriatly. > > However, when I tell JDE to compile it, it insists on cd'ing into > proj3/controller! and javac of course doesn't like that. As long as your classpath is set up correctly the cd command at the top of the compilation buffer should not matter. > > Is their any way to automate JDE's ability to know about packages so I > don't have to change the classpath for each project? Yes, you can set the jde-global-classpath for each project once and save it on a project file. Then JDE will take care of switching classpath when you switch projects. Javier
