Joerg Heinicke wrote:
Hello Cocooners,
I updated my local copy of Cocoon 2.1 with the current Fop release 0.20.5rc2.
There is lib/local folder for the local libs. Local is not (should not be) checked against jars.xml.
But this would not solve my problem, would it?
I updated the entry in jars.xml, but a CVS update always brings back the fop-0.20.4.jar.
<hack> You can overwrite old 20.4 jar with contents of your new 20.5rc2 jar; cvs update will then show "M" and won't get 20.4 back </hack>
Nice hack ;-) I emptied fop-0.20.4.jar to get the "M" and I removed terminate="yes" in the check-jars.xsl to avoid build failing. Is there a real issue behind the terminate="yes" for Jars not specified in jars.xml?
Joerg
Vadim
When building I get the following *warning*, which leads to *build failed* at the end, because of
<message terminate="yes">. Must the build process really be terminated, when there is only one jar to much?
Regards,
Joerg
--
System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de
