Ralph Goers schrieb: > Carsten Ziegeler said: >> 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. > > Really? I haven't been able to get a running portal on trunk in a while, > so I'll look forward to being able to have that back in a couple of days. > Ah, sorry, again one of my too short sentences: no, I'm not able to run the portal or any other block right now and I don't have a clue how to fix this. I meant that I need one or two days to replace ECM++ with Spring and then Cocoon runs again in the same way it runs today. Getting the blocks/samples run again is currently out of my scope for the Spring integration. But I really would love to have running stuff again :)
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
