Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
To: dev@ant.apache.org
Subject: Re: [PROPOSAL] Antlib Subproject
References: <20050211152332.59280.qmail@web30901.mail.mud.yahoo.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: Fri, 11 Feb 2005 16:32:58 +0100
In-Reply-To: <20050211152332.59280.qmail@web30901.mail.mud.yahoo.com> (Matt
 Benson's message of "Fri, 11 Feb 2005 07:23:32 -0800 (PST)")
Message-ID: <m34qgj5cyd.fsf@bodewig.bost.de>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through
 Obscurity, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Fri, 11 Feb 2005, Matt Benson <gudnabrsam@yahoo.com> wrote:

> I like it.

Great.

> My only concern at the moment is this: Am I correct that part of
> this effort (likely a very early part) would be the assigning of
> existing tasks/types to proper subprojects,

No, that's not intended (by me) at all.  If we ever want to farm out
existing Ant tasks into antlibs, that's fine.  I'm more concerned with
completely new tasks, that I'd like to offer a home in Ant-land
without adding even more stuff to Ant.

I can see good reasons to split out some of the tasks, but certainly
not all of them.  The whole bunch of SCM specific tasks could be
antlibs of their own, for example.  A release of Ant could then bundle
a specific release of these Antlibs.  This is an idea, but not the
driving force behind my proposal.

Stefan

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