Return-Path: 
 <cocoon-dev-return-39364-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 82297 invoked by uid 500); 28 Mar 2003 03:44:52 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 82282 invoked from network); 28 Mar 2003 03:44:52 -0000
Received: from out005pub.verizon.net (HELO out005.verizon.net)
 (206.46.170.143)
  by daedalus.apache.org with SMTP; 28 Mar 2003 03:44:52 -0000
Received: from verizon.net ([141.156.47.107]) by out005.verizon.net
          (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP
          id <20030328034501.HDFS14673.out005.verizon.net@verizon.net>
          for <cocoon-dev@xml.apache.org>; Thu, 27 Mar 2003 21:45:01 -0600
Message-ID: <3E83C539.8070801@verizon.net>
Date: Thu, 27 Mar 2003 22:44:57 -0500
From: Vadim Gritsenko <vadim.gritsenko@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: little problem with new build system
References: <3E822AB4.3080005@gmx.de> <3E82F853.6040209@verizon.net>
 <3E830761.2090908@gmx.de>
In-Reply-To: <3E830761.2090908@gmx.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from
 [141.156.47.107] at Thu, 27 Mar 2003 21:45:00 -0600
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

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