Hi,
I'm working with as part of a team in a Java project, and we would
like to share the prj.el (everything is in a source control system).
Problem is, some path definitions are different from one machine to
another. The JDK may be in a different directory, or the source control
mounting point (ClearCase in WinNT) maybe mapped to a different drive
letter. In that scenario what works for a developer will fail completely
for the other. Similar case when one want to work both from home and in
the office, and the machine configurations are not exactly the same.
I was thinking about using environment variables, but I don't know
how to better mix them with JDE. I used to change prj.el to make direct
calls to getenv when setting the path related variables. It works, but
then you lose the benefits of custom - which is not desirable.
I just started to try a different approach, where I mention the
environment variable names through custom and let the OS "solve" them
for me. So I would calls to setenv in a jde hook when loading the
project to make my customization. I'm afraid this approach will not work
in all scenarios, namely when the variable - for example
jde-global-classpath - is directly manipulated by a Lisp/Java aplication
instead of passed to the OS as part of a command line.
I think a third idea - haven't tried yet - would be to just have a
hook that completely obliterates the current value of the jde variables,
and set them from a local config file. But that seems too much of a
brute force approach, equivalent to have a separate prj.el for each
designer.
Any ideas?
TIA,
Nascif
