>
> It has a severe backwards compatability problem. All prj.el files
> everywhere except those that are at the root of project trees would have
> to have an explicit (jde-load-outer-project-file). The alternatives only
> require those jde users who are running on networked Windows machines do
> something.
I don't see why this is not backward compatible :(
The (jde-load-outer-project-file) could load the
outer prj.el file only if one existed.
So having that call inserted by the prj.el file
generator (due to the customize setting set to
'at-the-beginning' by default) at the top of
prj.el file, will exactly do what Paul's current
implementation does.
Only for people wanting a custom behaviour will require some
more work...
-sandip
