Daniel Fagerstrom wrote: > Yes, I think we should consider complicated class loading issues being > outside the scope of Cocoon 2.2. Yepp.
> > Right now I think that the main focus should be getting 2.2 release out > the door. What are the outstanding issues? As far as I can see, there are no outstanding *code* issues. The documentation needs some updates, but I think the most important topics are at least "covered". So we should just release the next milestone. > > Then we can start to work on using OSGi again. :) Or use something different (just kidding) :) Carsten -- Carsten Ziegeler - Chief Architect http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
