Heather Buch writes: > I think the users guide answered my question about this: > > "When you open a Java source file, the JDE looks for project files in > the directory tree containing the source file. If the JDE finds one or > more project files, it loads the project files in the > following manner. > > The JDE first sets all the JDE variables to their Emacs startup values > (i.e., the default value or the value saved in your .emacs file). It > then loads all the project files in the directory tree > containing the current source buffer, starting with the topmost file. > > What this means is that you can use project files to extend and/or > override the settings in your .emacs file and in other project files. > For example, your .emacs file can specify settings that > are common to all your projects. You can put settings common to a group > of projects at the top of the directory tree containing the projects, > settings common to each project at the top of the > directory containing each projects, and so on." > > Does this mean that a project global classpath extends a default global > classpath? No, the setting of jde-global-classpath in a prj.el file overrides the setting in the .emacs file.
If the project file for a project does not set jde-global-classpath, the current project inherits the setting of the nearest prj.el file up the source tree or if no prj.el file sets jde-global-class, the setting in the .emacs file, or if the .emacs file does not set jde-global-classpath, the setting of the CLASSPATH environment variable. - Paul
