I would suggest that new o.a.cocoon interfaces be used which, for the time being simply extend the existing interfaces. The use of the avalon/excalibur interfaces should be deprecated. This will allow the complete removal of Avalon/Excalibur in the future.
Ralph Carsten Ziegeler said: > Ralph Goers wrote: >> >> I encourage Carsten to wholeheartedly undertake this task. I >> really only have two thoughts. >> 1. I don't think it is a good idea to keep the same package >> names for ECM if they are moved into Cocoon. That could be >> very confusing. I realize it would be a lot of work to >> rename existing classes that use those interfaces, but done >> on the proper release boundary I think it is the right thing to do. > The implementation will get of course the o.a.cocoon package > names, so everything will be renamed. If course the marker interfaces > (Serviceable etc.) will not be renamed. > > Carsten > >
