Return-Path: <Arnout.Kuiper@nl.origin-it.com>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 99658 invoked from network); 21 Feb 2000 21:04:13 -0000
Received: from gw-nl1.origin-it.com (@193.79.128.34)
  by locus.apache.org with SMTP; 21 Feb 2000 21:04:13 -0000
Received: from mail.nl.origin-it.com (localhost.origin-it.com [127.0.0.1])
          by gw-nl1.origin-it.com with ESMTP id WAA10904
          for <ant-dev@jakarta.apache.org>;
 Mon, 21 Feb 2000 22:04:05 +0100 (MET)
          (envelope-from Arnout.Kuiper@nl.origin-it.com)
Received: from mail.nl.origin-it.com(172.16.127.67) by gw-nl1.origin-it.com
 via mwrap (4.0a)
	id xma010899; Mon, 21 Feb 00 22:04:05 +0100
Received: from nlehx900.ehvovh.nl.origin-it.com
 (nlehx900.ehvovh.nl.origin-it.com [172.16.92.111])
	by mail.nl.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id WAA04768
	for <ant-dev@jakarta.apache.org>; Mon, 21 Feb 2000 22:04:04 +0100 (MET)
Received: by NLEHX900.origimail.origin-it.com with Internet Mail Service
 (5.5.2448.0)
	id <1H29J523>; Mon, 21 Feb 2000 22:04:04 +0100
Message-ID: 
 <E1B81A5627BAD01191B500805FC16B0E77AADA@nlnwx001.origimail.origin-it.com>
From: "Kuiper, Arnout" <Arnout.Kuiper@nl.origin-it.com>
To: "'ant-dev@jakarta.apache.org'" <ant-dev@jakarta.apache.org>
Subject: RE: Ant project versus jmk (Java in Make)
Date: Mon, 21 Feb 2000 22:04:01 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

I used jmk in the past, but I stopped using it because it was too much
hassle. The
projects I work upon are really big, with lots of packages and files. It was
a
hell of a job to keep the makefiles up to date.

With Ant, I have one simple build-file that does it all for me, with little
or no
maintenance. There is only one feature of jmk that I miss in Ant, and that
are the
compile dependencies.

This feature could be put in the Javac task. I would separate the
dependency-file
from the build-file (such that it can be (re)generated automatically (I
wrote a
utility for that a while ago, which could be promoted to a task when
preferred).
The format of the dependency file can be anything. I would prefer XML a-la:

<dependencies>
  <file name="pckg/xyz.java">
    <depends name="pckg/test.java">
    <depends name="pckg/abc.java">
  </file>
  ...
</dependencies>

The logic could be placed after the selection of files based on date. Just
add
the files that are dependant on files on the list to that same list.

This would save me a couple of clean rebuilds each day.

How about this?

Cheers,

  Arnout