You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by James Cook <ji...@iname.com> on 2000/11/27 14:14:22 UTC
Target exposing Tasks?
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?
jim
Re: Target exposing Tasks?
Posted by Stefan Bodewig <bo...@apache.org>.
James Cook <ji...@iname.com> wrote:
> 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.
Yes I know, but then Antidote is far from complete yet, Simeon has
only started working on it three weeks ago.
> I would like Ant integration in my tool to be a little more
> dependent on Ant, and less on a bundled GUI.
Conor has already put that right. I didn't mean to say "go use
Antidote" but "Antidote faced the same problem so Simeon proposed to
change Ant's core". Sometimes I need sonmebody who rephrases my words
to get some meaning out of them, thanks Conor 8-).
Stefan
Re: Target exposing Tasks?
Posted by James Cook <ji...@iname.com>.
----- Original Message -----
From: "Conor MacNeill" <co...@ebinteractive.com.au>
> Unless, I misundestood you, of course :-)
Maybe a little. :-)
I wasn't planning on using Antidote, but when I saw that it parses the build
script and loads properties, I was concerned with why they chose that path. I
was worried that there was a strong design decision to go this route. Since I am
not taking this route, (as I am using the objects that Ant creates), I was
concerned that my approach was not going to work somewhere down the line.
I see that the Project at least exposes its Targets now. I don't have the source
in front of me, but I don't believe that Target exposes its Tasks yet, but
that's trivial. I will have to get intimate with the IntrospectionHelper to make
sure I correctly identify valid attributes for a task.
I too am building a graphical interface for Ant. I am planning on integrating it
into JBuilder, but I am designing it so that it will run standalone as well. I
don't want to build or run your GUI until I am done. It will be interesting to
see the differences in the two products.
jim
RE: Target exposing Tasks?
Posted by Conor MacNeill <co...@ebinteractive.com.au>.
Jim,
I think you may have misunderstood Stefan. The change you desire is
something that Simeon also wants to see for antidote. This does not mean
that you would need to use antidote to see a target's tasks. This will be a
core ant service.
Unless, I misundestood you, of course :-)
Conor
--
Conor MacNeill
conor@cortexebusiness.com.au
Cortex eBusiness
http://www.cortexebusiness.com.au
> -----Original Message-----
> From: James Cook [mailto:jimcook@iname.com]
> Sent: Tuesday, 28 November 2000 12:22
> To: ant-user@jakarta.apache.org
> Subject: RE: Target exposing Tasks?
>
>
> 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 <ji...@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
>
>
RE: Target exposing Tasks?
Posted by James Cook <ji...@iname.com>.
I looked a little closer at the Ant source and I see that the changes I was
looking for *are* already in the source. So why is the Antidote team parsing
the build scripts separately? Or are they?
jim
-----Original Message-----
From: James Cook [mailto:jimcook@iname.com]
Sent: Monday, November 27, 2000 8:22 PM
To: ant-user@jakarta.apache.org
Subject: RE: Target exposing Tasks?
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 <ji...@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
RE: Target exposing Tasks?
Posted by James Cook <ji...@iname.com>.
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 <ji...@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
Re: Target exposing Tasks?
Posted by Stefan Bodewig <bo...@apache.org>.
James Cook <ji...@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