>>> Paul Kinnucan <[EMAIL PROTECTED]> 10-Nov-00 9:25:48 PM >>>
>I mean distribute your improvements as a uniquely named
>file containing only your code. (I'm assuming that your code
>is standalone and does not entail changes to the existing
>jde-compile code.)
Ok. I'm doing that now.
>Or you could include your relative path stuff in the separate
>compile file and then wait until the general path release to
>incorporate your compile stuff into the JDE distribution.
But that's my point. The relative stuff breaks existing behaviour
(because any relative definition would). So can you distribute it
because anybody using it and then throwing it away would be stuck with
relative paths that wouldn't work.
I don't think that's a problem personally... users will just have to
re-edit them but I presumed that's why you were saying you didn't want
the relative path change.
Nic
