Hi Andy, No, there isn't much that you do directly with the cactifywar task. It could honor the update attribute from the WAR task but that would required a patch.
I think the best is to think in term of the other options you have to speed up your development. The first thing for rapid development is to not use the cactifywar task at all. You could have an expanded war that you directly put in your container's webapps directory. And you shouldn't start/stop your container at each run. Simply leave it running. Basically this means not using the <cactifywar> and <cactus> tasks. You would use the <junit> task to run your cactus tests. In the future it would be a good idea to support this mode of development directly in the <cactifywar>/<cactus> tasks. Thanks -Vincent > -----Original Message----- > From: Andy Kriger [mailto:[EMAIL PROTECTED] > Sent: mardi 18 janvier 2005 18:42 > To: [email protected] > Subject: cactifywar is slow > > Is there a way to speed-up the cactifywar Ant task or to workaround > running it every time you rebuild your war file with new test classes? > It can take several minutes to run which really slows down rapid > development of in-container tests. > > Any advice? > > Thanks > andy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
