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 (athena.apache.org: local policy)
To: dev@ant.apache.org
Subject: Re: EasyAnt project
References: <974992.67483.qm@web55104.mail.re4.yahoo.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: Wed, 29 Oct 2008 16:51:41 +0100
In-Reply-To: <974992.67483.qm@web55104.mail.re4.yahoo.com> (Matt Benson's
 message of "Wed\, 29 Oct 2008 08\:21\:11 -0700 \(PDT\)")
Message-ID: <y1uiqrbjt6a.fsf@v30161.1blu.de>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Wed, 29 Oct 2008, Matt Benson <gudnabrsam@yahoo.com> wrote:

> I am thinking a less invasive approach would be:

Sounds good to me.

> 1.  Allow arbitrary properties of a Target object to
> be set using IntrospectionHelper.
> 2.  Delegate Target instantiation to Project.

Why?

I have a toy project that I hope to be pushing into the sandbox sooner
or later which contains a custom ProjectHelper.  It heavly relies on
the ProjectHelper to be able to create its own subclass of target.

> 3.  Define an ant.project.class magic property to
> easily allow the user to specify an extended Project
> class to use.
> 4.  EasyAnt has its own Project, Target, and Executor
> implementations that know about phases.

If EasyAnt used a ProjectHelper of its own, it probably could get away
without a custom Project.  A custom Executor may be a good idea,
though.

EasyAnt would need its own wrapper script or an invocation would
become cumbersome, though.

Stefan

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