ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 4937] - Checkpoints for builds
Date Sun, 18 Nov 2001 01:43:33 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4937>.
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 -------
<uptodate> 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...
<target name="prepare"/>
<target name="compile" depends="prepare"/>
<target name="jar" depends="compile"/>
<target name="javadoc"/>
<target name="dist" depends="jar,javadoc"/>

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message