Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <001e01c043e0$9f542100$2a2a2a0a@ns2000>
From: "Nico Seessle" <Nico.Seessle@epost.de>
To: <ant-dev@jakarta.apache.org>
References: <20001031154159.5936.qmail@web2302.mail.yahoo.com>
 <39FEE910.616E7DA2@gmx.net>
Subject: Re: Home for ANT GUI (was: Ant GUI Requirements)
Date: Wed, 1 Nov 2000 09:49:18 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Toby Baier" <Toby.Baier@gmx.net>
To: <ant-dev@jakarta.apache.org>
Sent: Tuesday, October 31, 2000 4:45 PM
Subject: Re: Home for ANT GUI (was: Ant GUI Requirements)


> > Actually, I like this approach quite a lot. The GUI
> > can have it's own build file, and since the src.dir
> > property in the Ant build files is src/main, the GUI
> > state won't affect the build and deployment of Ant
> > (until we wanted it to).
> > 
> > If the group is amenable to this, I'd like to go for
> > this approach. If at some point the GUI grows in scope
> > it can always be moved out to its own project, whereas
> > going straight for project status takes effort and
> > time that may not be well spent this early on.
> > 
> > Thoughts?
> 
> +1
> 
+1