Re: Centipede build.number

Unico Hommes wrote, On 31/03/2003 16.43:
> I have also seen some strange behavior from the buildnumber task. One 
> time I watched it jump from 226 to 0 in the next run. But it's not only 
> an ant problem because if there are project dependencies in the module 
> then for each new project run the buildnumber gets increased. When you 
> really only made one build invocation. This is because for every such 
> dependency CentipedeTask runs an <ant antfile="centibuild.xml" /> and 
> since buildnumber is global (ie. not in any target) it gets executed 
> every time.

Correct.

> I think that maybe some of these global initialisation tasks could be 
> factored out into an init task that gets executed only once. For 
> instance all the file imports, the taskdefs, a lot of the properties, 
> etc. 

I already tried this at some point, but unfortunately it did not work. 
IIRC it was about the fact that antcall actually uses a new Ant version, 
but I don't remember the details, they should be in the mail archives.

> Also the CentipedeTask.runProject could execute the dependent 
> project using a CallTarget task instead of Ant task. I've tested this 
> and is seems to work.

Yes, it should work. Are you seeing speed increases in that case?

-- 
Nicola Ken Barozzi                   [email protected]
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------



-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/