ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Cook" <jimc...@iname.com>
Subject RE: Target exposing Tasks?
Date Tue, 28 Nov 2000 01:22:28 GMT
Looking at the latest source snapshot, the antitode project seems to not
care about using Ant's Project|Target|Task objects, but rather it parses a
project from scratch.

I would like Ant integration in my tool to be a little more dependent on
Ant, and less on a bundled GUI. Perhaps this is a shortterm design
workaround for the time being, but it seems that they spent a good deal of
time on it. Is this the direction for Antidote? If so, what's the rationale?

For my needs (and other integrators) I would propose that the Project,
Target, and Task objects expose their collections in Ant. I will make the
change on my local model and I can post a patch if this makes sense to the
committers. It's pretty simple if a committer chooses to do this on their
own. It's more of a design decision, I suppose.

jim

-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@apache.org]
Sent: Monday, November 27, 2000 9:47 AM
To: ant-user@jakarta.apache.org
Subject: Re: Target exposing Tasks?


James Cook <jimcook@iname.com> wrote:

> Shouldn't the Target object expose its Vector of Task objects? How
> are people attempting to integrate Ant into their Tools getting the
> list of Task's for a given Target?

Recent CVS sources do - or at least Simeon has proposed to make the
change and I haven't seen any objections. It's for exactly this
purpose so that Antidote (the new GUI for Ant) can get a list of
tasks.

Stefan


Mime
View raw message