Supporting environment variables is a great improvement for team environments; I tried to do it by playing directly with the elisp code inside prj.el, but it was conflicting with the use of customize.
I'm following the on-going discussion about this topic in the jde list; I'll be glad to test the new modules in my environment and provide some feedback.
Regards,
Nascif
-----Original Message-----
From: Nic Ferrier [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 10, 2000 12:33 PM
To: Abousalh-Neto, Nascif [NCRTP:JA45:EXCH]
Cc: [EMAIL PROTECTED]
Subject: Re: project based compilation
>>> "Nascif Abousalh-Neto" <[EMAIL PROTECTED]> 10-Nov-00
5:21:28 PM >>>
>The relative path is a great idea. We use ClearCase in NT,
>and every designer has the "views" mounted as different
>paths (different drives/path names). The result is that we
>can't share prj.el files. This is a wonderful change. We tried
>to use things like ../../../myDirectory, but it is just to
>error prone.
Cool.
Note that my jde-compile.el also handles the substitution of
environment variables so you can do this:
classpath $CLASSPATH
>How hard would it be to extend the relative path idea to
>other variables that hardcode source paths, like
>jde-db-source, etc.?
Not that hard... but as Paul pointed out in an earlier mail there are
*a lot* of places.
If volunteers were to help me build a list of places this needed to
be done it could actually be done quite quickly.
We'd need to test it afterwards of course, on a varierty of different
platforms.
Nic
