forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ferdinand Soethe <>
Subject Re: Plans for integrating FOP .94
Date Tue, 11 Dec 2007 11:58:06 GMT
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 :-)

> ..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 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? Can I build the needed blocks
individually? Should I try another version?


>> 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

View raw message