* Antcontrib <trycatch> * Ant2 will never be written * why you dont check for the existence of the webapp before undeploying?
Jan >-----Ursprüngliche Nachricht----- >Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Gesendet: Donnerstag, 18. August 2005 12:31 >An: [email protected] >Betreff: Workaround for no failonerror > >I keep needing to ignore failures for tasks which don't >themselves support a "failonerror" attribute. > >For example, I want to add a tomcat 'undeploy' task when doing >a clean build before redeploying the newly built warfile to tomcat. > >But this fails if the the app is not already deployed, and >stops the clean and build halfway through. So I keep having to >go in and edit the build.xml to switch this task in and out manually. > >The feature inlined below is accepted for Ant2, but Is there a >recognised way already in use to enclose an arbitrary task in >some kind of wrapper which swallows (ignores) errors where >they don't matter, allowing the build script to continue? > >I am using Ant 1.6.2 embedded in Eclipse. > >Cefn >http://cefn.com > >>>>>>>>>>>>>>>>>>>> > >From <http://ant.apache.org/ant2/requested-features.html> >http://ant.apache.org/ant2/requested-features.html - accepted >new features.... > >'Provide "failonerror"-like functionality to all tasks. >(Provide this as an aspect?? Much like logging aspect or >classloader aspect).' > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
