I certainly agree that NAnt being fully transactional is probably not appropriate.
One thought.... NAnt currently offers target dependencies. How about an additional set of target dependencies to be run on a failure? That way your build script could supply an appropriate rollback target if necessary. Regards, Richard -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bevan Arps Sent: Tuesday, January 25, 2005 14:13 To: [EMAIL PROTECTED] Sourceforge. Net Subject: RE: [Nant-users] Transactionality in NAnt > I agree that a build is not a deployment, but I do believe a build can > be a component of a deployment. I am also looking to use NAnt as both a build tool and a deployment tool. (Haven't got there yet, still setting up infrastructure). I disagree, however, with the premise that NAnt should be fully transactional. Why? For NAnt to be fully transactional, every task needs to have built in "smarts" to support rollback. [Rest of message snipped] ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
