javac and jar check existence of files before running, whereas javadoc doesn't. Avoiding unnecessary processing requires using a dedicated check target with a uptodate task. On the same idea, creating a tar.gz archive requires a tar, a gz, and then a delete task. Running the target a second time check for the tar file, and exec again as it is absent. Once again, a check in a dedicated target could be used. In both cases, having to rely on custom check is rather ugly. Why not include an automatic check in javadoc task, and create a full tar.gz task ? -- Guillaume Rousse <[EMAIL PROTECTED]> GPG key http://bohm.snv.jussieu.fr/~rousse/gpgkey.html
