little problem with new build system

[Joerg Heinicke <jo...@gmx.de>]

Hello Cocooners,

I updated my local copy of Cocoon 2.1 with the current Fop release 
0.20.5rc2. I updated the entry in jars.xml, but a CVS update always 
brings back the fop-0.20.4.jar. 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


D:/cocoon-2.1/tools/src/check-jars.xsl:110:40: Warning!
   File fop/lib/fop-0.20.4.jar appears in the lib/ directory, but is not 
declared in lib/jars.xml.

   Please update the lib/jars.xml file to include the 
fop/lib/fop-0.20.4.jar file together with a description.

: Fatal Error! Stylesheet f³hrte zu Beendigung
: Fatal Error! Fatal error during transformation Cause: Fatal error 
during transformation
Failed to process D:\cocoon-2.1\lib\jars.xml

BUILD FAILED
file:///D:/cocoon-2.1/src/targets/validate-build.xml:51: Fatal error 
during transformation

Re: little problem with new build system

[Vadim Gritsenko <va...@verizon.net>]

Joerg Heinicke wrote:

> Vadim Gritsenko wrote:
>
>> Joerg Heinicke wrote:
>
...

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

Answering your question above: it can (see option 2). You have two choices:
1) Overwrite old library: cp ~/fop-20.5rc2 $COCOON_HOME/lib/fop-0.20.4.jar
2) As you said, empty old library and put new under lib/local. No need 
to modify stylesheet.

And terminate=yes is to keep jars.xml up-to-date, but this is/was 
discussed in the other thread.

Vadim

Re: little problem with new build system

[Joerg Heinicke <jo...@gmx.de>]

Vadim Gritsenko wrote:
> 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
joerg.heinicke@virbus.de
www.virbus.de

Re: little problem with new build system

[Vadim Gritsenko <va...@verizon.net>]

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.


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

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