Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 87300 invoked from network); 18 Nov 2001 01:43:29 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 18 Nov 2001 01:43:29 -0000 Received: (qmail 27455 invoked by uid 97); 18 Nov 2001 01:43:34 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 27438 invoked by uid 97); 18 Nov 2001 01:43:33 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 27425 invoked by uid 50); 18 Nov 2001 01:43:33 -0000 Date: 18 Nov 2001 01:43:33 -0000 Message-ID: <20011118014333.27424.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: ant-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 4937] - Checkpoints for builds X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4937 Checkpoints for builds ------- Additional Comments From sbailliez@apache.org 2001-11-17 17:43 ------- task might help you to do what you want. I use it for example to avoid generating code blindly. Alternatively a large build file is normally splitted into several targets that depends on each other, so there is normally always the possibility to perform a somewhat atomatic operation, it is up to the build.xml writer to do this correctly. For example, assuming I have a dist target that takes time and that it fails, to compile, I can simply compile or jar... -- To unsubscribe, e-mail: For additional commands, e-mail: