RE: Centipede build.number

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.
 
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. 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.
 
Regards,
Unico
 

	
	
	
  _____  

	From: Adam Jack [mailto:[email protected]] 
	Sent: zaterdag 29 maart 2003 16:05
	To: [email protected]
	
	
	I am no expert, but this is an ant thing, not a centipede thing per se.
	 
	http://ant.apache.org/manual/CoreTasks/buildnumber.html
	 
	I suspect that somewhere in the complexity of processing that your centipede configuration is performing this is somehow getting invoked more than once. [This last sentence is a guess.]
	 
	regards
	 
	Adam

		-----Original Message-----
		From: [email protected] [mailto:[email protected]]On Behalf Of Paul O'Neill
		Sent: Friday, March 28, 2003 9:58 AM
		To: krysalis
		Subject: Centipede build.number
		
		
		Hi,     
		    has anyone noticed any strange behaviour of the build.number file/value.
		for me sometimes to seems to do more than increment after each build/build attempt.
		e.g it jumps from 53 - 104 after 1 build
		 
		Thanks,
		Paul.

		Paul O'Neill . · ´ ¯ ` ® 
		Software Engineer                DDI: (01) 2400 522 
		Online Travel Solutions         Tel:(01) 2400 500 
		Sabre                                  www.sabre.com <http://www.sabre.com/>