Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
To: user@ant.apache.org
Subject: Re: PropertyFile task is optional?
References: <20050128160916.99781.qmail@web30906.mail.mud.yahoo.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: Fri, 28 Jan 2005 17:33:54 +0100
In-Reply-To: <20050128160916.99781.qmail@web30906.mail.mud.yahoo.com> (Matt
 Benson's message of "Fri, 28 Jan 2005 08:09:15 -0800 (PST)")
Message-ID: <m3hdl15x8t.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, 28 Jan 2005, Matt Benson <gudnabrsam@yahoo.com> wrote:

> Indeed, I have myself wondered (though I never have
> bothered to bring it up) why propertyfile and
> echoproperties are an optional tasks when they have no
> external dependencies?
> 
> Any old-timers have any insights?

Unless Conor jumps in, it won't get any older than me.

These tasks are by far not the only tasks that are listed as optional
but don't have any external dependency.  At one point in time we used
the core vs. optional distinction much the same way we now use "part
of Ant's distribution" vs. "ship as an antlib".  Some tasks simply
ended up in optional because they weren't considered *that* useful for
the broad audience.

It's been a long time since anybody brought up the "why is X optional"
question.  I guess most people have settled with, "it is called
optional, but it is always there" by now.

Stefan

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