You could always hack this sort of thing with creating/destroying "dummy" files to let you know where things are, or mark state in a properties file using <propertyfile> and such.
----- Original Message ----- From: "Krueger, Tom" <[EMAIL PROTECTED]> To: "Ant Users List" <[EMAIL PROTECTED]> Sent: Friday, January 18, 2002 9:38 AM Subject: RE: Start/Restart I was hoping to use it for more than builds, due to Ant having alot of, if not all the functionality I need with the exception of Start/Restart. I was looking to have it kick off jobs such as unloading data. If the second step in the process fails, I don't want to redo the successful steps (unload data as an example). Thanks for the help. -----Original Message----- From: Ylan Segal [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 4:10 PM To: Ant Users List Subject: RE: Start/Restart > I am looking to have it work a little differently. > > if Target C depends on B and A and A and B succeed but C failes.. > Then the next time it is started I would like it to run C. > > Basically, if some thing fails, I would like it to skip all the targets > that have already run successfully. What do A and B do? For example if they compile come sourcecode, the next time it runs, although the target will get called, it won't do anything as everything is compiled already. Same goes for copy, which will only copy newer files (by default), etc. Does that help any? Ylan Segal. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
