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.
* JDEbug turns off context-switching when the debugger is running to avoid
losing
track of the source pointer when stepping through code.
- Paul
