On Tue, 2007-12-11 at 12:58 +0100, Ferdinand Soethe wrote: > Thorsten Scherler wrote: > > Thanks Thorsten. That helped quite a bit. > > > Did you try to "just" add commons logging as well (drop the lib)? > > I'd try if I knew where to find that lib :-)
http://commons.apache.org/logging/ > > > ..or (better) update our cocoon version to the current cocoon one or > > switch to cocoon-2.1.x. Otherwise we are really starting to fork cocoon. > > That makes sense in context of what you write below. > So should I do that? And how do I get started. I would try 2.1.x. First by using our files http://svn.apache.org/viewvc/forrest/trunk/etc/cocoon_upgrade/ to build the jars that we need and then replace the ones we have in http://svn.apache.org/viewvc/forrest/trunk/lib/core/ After this a clean build of forrest and see what errors are thrown. > > I installed maven and checked out Cocoon trunk last night. > But building repeatedly failed with the message > > > Failed tests: > > > > testRefreshSyncURI(org.apache.cocoon.components.source.impl.CachingSourceTestCase) > > Is there a better way? http://svn.apache.org/viewvc/cocoon/trunk/README.txt?view=markup mvn -Dmaven.test.skip=true install The important part is the "-Dmaven.test.skip=true" property, since the error that you see is coming from a test. > Can I build the needed blocks > individually? yes. cd to the directory. mvn -Dmaven.test.skip=true install > Should I try another version? No, you would need to try with trunk. salu2 > Thanks, > Ferdinand > > > > >> Now could somebody perhaps explain to me in simple terms how > >> to best accomplish that (recompile that block)? > > > > I think that is not that easy, since they did not only switch the > > container but as well they building engine (now maven). > > > > Basically you need to get our cocoon revision and then manually patch > > the FOP block from our revision to current HEAD of the block. You need > > to analyze every single change and decide whether or not it is container > > related, since you do not want any changes that are using Spring > > features. > > > > That leaves you with a forked FOP block that should be build with ant > > instead of maven. Then you need to find the old documentation how to > > build a block (I reckon looking at the 2.1.x docu may do). > > > > The task is not that trivial and leaves us with a fork. > > > > HTH a wee bit. > > > > salu2 > > > >> Thanks, > >> Ferdinand > >> > -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
