Daniel Fagerstrom wrote: > It depends on how long time you think that it will take. If you think > that it take a week or so I suggest that you branch cocoon-core, and > work on the branch until it works again and merge it back then. In the > meantime the rest of us try to avoid doing larger changes in cocoon-core > trunk. > > If it takes like a month or so, it is better to try to do some splitting > of cocoon-core first, so that you only need to branch the tree-processor > and the top layer that contain the Cocoon object. Ok, I think this will take one or two days until Cocoon runs again while it might take a little bit longer to polish everything.
> > In any case it must be done in a branch. We are making good progress > with the blocks work, and having a cocoon-core that doesn't would be a > far to large disruption. > I'm wondering if I'm changing the right place. Now the switch to Spring is finished cocoon-core will look different (less use of Avalon). Now, has this any influence on the blocks implementation like block-fw? I looked there briefly and saw that for example ServiceManager is used there for getting components from a block. We should change that as well and perhaps use our own interface? And if the cocoon-core uses Spring what has to be done in the blocks-fw? Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
