ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cook, Levi" <levi.c...@kraft.com>
Subject Re: FW: tar task blues
Date Mon, 02 Jul 2001 14:11:32 GMT
Thanks for the tips-- Figuring out how to design around immutable properties
was a fairly tricky issue at first, but it seems quite sensible now.

I've attached my script, which works great for me, minus the apparent errs
made by the tar task.

As far as property initialization goes, I'm not passing in any -D options,
and pull info from the following two properties files:
<property file="${user.home}/${ant.project.name}.build.properties"/>
<property file="build.properties"/>

The first is currently blank-- The second is as follows:

### Contents of build.properties
# build.compiler=jikes
vss.ssdir=c:/program files/microsoft visual studio/vss/win32
vss.login=xxx,xxx

 <<build.xml>> 

Thanks again,
Levi Cook


> -----Original Message-----
> From: Peter Donald 
> Subject: Re: FW: tar task blues 
> Date: Fri, 29 Jun 2001 22:45:55 -0700 

> On Sat, 30 Jun 2001 06:19, Cook, Levi wrote:
>> Ooops.. I sent before I was done typing my message :)

> ;)

>> Among other things, it overrides the fixcrlf applied in the previous step
>> of this target, which results in .sh scripts with DOS line terminators.
:(
>> Can anyone confirm this behavior? or suggest an ant based fix?

> This sounds vaguely like an issue relating to immutable properties. 
> Properties are immutable so when you do something like

> <property name="tar.tmp.dir" value="${dest.dir}/tar-tmp-dir"/>

> It will only set this to correct value first time though. Consequently if
you 
> were to run fixcrlf it will always use this value. Could this be the
cause?

> BTW it is kind of difficult to diagnose your problem given snippet used - 
> could you send the full build file (either on list or to me directly if it
is 
> large).

> Cheers,

> Pete

Mime
View raw message