Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Message-ID: <40C7662C.2040506@umn.edu>
Date: Wed, 09 Jun 2004 14:34:04 -0500
From: Tony Collen <colle006@umn.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: cocoon install
References: <40C75288.8000604@perfectorder.com> <40C75382.2050509@enst.fr>
 <E2CEF0FD-BA49-11D8-B44B-003065E54496@perfectorder.com>
 <40C7638B.4040605@umn.edu>
In-Reply-To: <40C7638B.4040605@umn.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Tony Collen wrote:
> Pablo wrote:
> 
>> OK I figured it out.  A bash shell user wrote the build.sh . How can 
>> I  tell .  Because build.sh is written in shell and the export 
>> commands  are in bash shell format.
>>
>> for example you can NOT  write the following in shell script
>> export ANT_HOME=tools
>>
>> rather you have to write
>> ANT_HOME=tools ; export ANT_HOME
>>
>> You can see this all over the build.sh shell script. So for anybody  
>> searching the archives that are having the same problem now you know.
>> -Pablo
> 
> 
> Thanks, I'll work on fixing this... next time feel free to file a bug or 
> send a patch of your own ;)


Actually, this has been fixed in CVS already since 2.1.5 was released, which explains why I couldn't 
find the export statements in my copy of the code:

http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/build.sh?r1=1.12&r2=1.13&diff_format=h

Tony


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org