Re: cvs commit: avalon-excalibur/io/src/xdocs index.xml menu.xml

[email protected] wrote:
> In article <[email protected]>, "Berin Loritsch"
> <[email protected]> wrote:
> 
>>...
>>What do you mean before compatibility is in place?  Are you saying we
>>cannot move anything until all our dependent projects notify us and tell
>>us that they are ready?
>>
>>Can we handle a temporary incompatibility that lasts for a day--or at
>>the most two?
> 
> 1) revert the changes to restore compat
> 2) come up with another mechanism to establish back-compat
>    (some kind of extra jar containing deprecated code(?) is what I think
>     Berin suggested; I'm obviously out of my element here :-)

Apparently ANT is stricter about requiring all path elements to exist
in CVS--which is why the GUMP build failed last night.

Hopefully I have resolved these issues for the compatibility and
lifecycle packages