At 02:46 AM 8/10/2001 +0200, you wrote:
>Hi!
>
>I have the following project file:
>
This does not look like a project file to me. It looks like a .emacs file.
I would suspect that you actually do not have a project file in your source
hierarchy, in which case the JDE would treat relative paths as relative to
the directory of the current source buffer, which appears to be the
behavior you are experiencing.
- Paul
P.S. using setq to set JDE customization variables usually leads to
problems. Please read the JDE user's guide section on customizing JDE
variables.
>
>(setq jde-resolve-relative-paths t)
>(defvar tmp-javacode-dir "~/javacode-tmp")
>
>(defvar cp '("./"
> tmp-javacode-dir
> "./../../../lib/ejb.jar"
> "$JIKESPATH"))
>
>(custom-set-variables
> '(jde-global-classpath cp)
> '(jde-compile-option-directory tmp-javacode-dir) ;; necessary for all the
>completion commands
> '(compile-command (concat "~/root-room-access/build.sh"))
>)
>
>
>I think I followed the rules described in the documentation, I don't
>want to use absolute path in my project file. The problem is: When I
>invoke the comiler, the paths are interpreted relativly to the file I
>want to compile and not to the project file. Because I don't know what
>structure my source code directory will habe, I don't see any way to
>write a portable project file. The solution would be treating the
>paths relativ to the location of the project file.
>
>Any suggestions??
>
>By Stefan
