1 Jul 01:41
Re: Cocoon-fop-impl using old version of fop.jar
Kamal Bhatt <kbhatt <at> tt.com.au>
2008-06-30 23:41:27 GMT
2008-06-30 23:41:27 GMT
This has been done in trunk (I think) https://svn.apache.org/repos/asf/cocoon/trunk/blocks/cocoon-fop/cocoon-fop-ng-impl/ I don't know why this hasn't been released, a committer can give more information on what needs to be done to make this a stable, released block. Unfortunately, when the Fop crew moved to 0.9x they completely rewrote the API for embedding which makes the upgrade a little more difficult than simply changing the version number. Also, 0.9x works very differently to 0.20.5. From my understanding 0.20.5 had many deviations from the XSL FO standard, which were rectified in 0.9x. This means that there are probably many people out there who would scream bloody murder if we simply moved to 0.9x as all their stylesheets would break. I assume the reason why both 0.20.5 and 0.9x were not supported in the same transformer was because of clashing classes. For more details see here: http://xmlgraphics.apache.org/fop/0.94/upgrading.html > Hi guys, > > > > Any particular reason why we still use the DINO-version of the fop.jar > (0.20.5) ?(Continue reading)
But at least it helped me to write about it - it finally solved my
blindness.
Felix
> Hi all
>
> I stated some problems using not yet released blocks mixed with the
> released c22 ones.
>
> Having an application based on the released c22 core stuff but using
> some non released 'SNAPSHOT blocks I stated that I
> wasn't able to use the SNAPSHOT blocks because they are wired with the
> cocoon-core snapshot.
> Building and deploying locally the snapshot blocks and then using them
> maven also wants to pull in the latest
> cocoon-core 2.2.1-SNAPSHOT (probably because of parent poms).
>
> Can't we base for the non released blocks on the released cocoon-core
> 2.2 where possible?
>
> WDOT?
>
> Felix
>
> PS:
RSS Feed