> -----Original Message-----
> From: EXT Paul Kinnucan [mailto:[EMAIL PROTECTED]]
> Sent: Dienstag, 9. Mai 2000 22:51
> To: Rich Johns; jde
> Subject: Re: project files
>
>
> At 03:22 PM 5/9/00 -0500, Rich Johns wrote:
> >nt4.0
> >jde2.16beta23
> >jdk1.3
> >
> >I've recently changed my jde usage patterns. Lately I'm doing a lot
> >more setting the compile/run classpath on a per project
> basis, whereas
> >before
> >I set my environment variable CLASSPATH to be everything I needed.
> >
> >Anyhoo, I've got buffers occupied by files from multile projects,
> >each(project) with
> >its own prj.el. My expectation is that each time I switch
> buffers, the
> >prj.el file associated with the file will be effective.
> However, when I
> >compile
> >the buffer I get the classpath from the previous buffer,
> which was part
> >of another
> >project.
> >
> >I get around this by doing a load project file. But, I
> thought this was
> >automatic.
> >Do I have things set up incorrectly? Or is this the way it is
> >(presumably for a good
> >reason that I'm not thinking about :-)
>
>
> Project context switching typically fails for one of the
> following reasons:
>
> * You did not give each project a unique name when you
> initially created
> the prj.el file for
> that project.
>
> To verify this, look at the first line of each project
> file. It should read
>
> (jde-set-project-name "UNIQUE_NAME")
>
> where UNIQUE_NAME stands for the actual name of the
> project. The actual
> name can be any
> unique string.
Hi JDE-junkies ;-)
It's the first time i heared or read about that parameter. Nothing in the
User's guide or somewhere else in the doku. It isn't even configurable via
the Customize buffer and therefore is not included in dumped project
settings (in .emacs).
I checked out your hint, but it seems not to work.
To validate, plz take the attached zip and extract it anwhere you want, but
into the same parent directory. This zip contains the following files and
directories:
- dir "new"
- dir "new/src"
- dir "new/bin"
- file "new/prj.el"
- file "new/src/TestNew.java"
- file "new/bin/TestNew.class"
- dir "old"
- dir "old/src"
- dir "old/bin"
- file "old/prj.el"
- file "old/src/TestOld.java"
- file "old/bin/TestOld.class"
Now perform the following steps:
1) Load file "old/src/TestOld.java"
Emacs will load the correct prj.el file.
2) Compile it.
Updated (with new time stamp) class file will end up in dir "old/bin/".
3) Now load file "new/src/TestNew.java"
Emacs will load the correct prj.el file.
4) Compile it.
Updated (with new time stamp) class file will end up in dir "new/bin/".
So far, so good. But now,
5) Switch back to buffer "TestOld.java" and compile it.
Now JDE will use the poject settings valid for "TestNew.java".
Thus, "TestOld.class" ends up in directory "new/bin/" which was definitely
not
what the project files intended to configure.
BTW, I revealed this odd behaviour with
- Windows NT SP6
- GNU Emacs 20.6.1 (i386-*-nt4.0.1381)
- JDE 2.16 beta23
Or is it a configuration error?
Sincerely,
Michel
Test.zip
