I think these getters arent there because we havent needed it :-)
Only the target class itself uses these information so why putting them in?
But if there is a need for having getters outside I don´t see an obstacle
while
adding them ... the information are not unofficial ...
Do you need more?
Jan
> -----Original Message-----
> From: Christophe Labouisse [mailto:ant-ml@ggtools.net]
> Sent: Tuesday, June 01, 2004 10:59 AM
> To: dev@ant.apache.org
> Subject: Using Ant API to retrieve task/target information
>
>
> Hi,
>
> I'm the writer of the Grand tool
> (http://www.ggtools.net/grand) and since
> I came upon some issues with the Ant API I'd like to have some more or
> less "official" advice about the way I use it.
>
> I started Grand shortly after Ant 1.6.0 was released since the
> visualization tools I used where all broken. I find out that
> the Ant API
> was providing all I need to do a basic dependency graph and
> will allow me
> not to duplicate "things" already done by ant such as XML parsing,
> importing targets, etc. Beside using the API allow to display
> dynamically
> created targets. Soon I needed to handle calls such as the
> one created by
> ant or antcall. This was a little bit more complicated and I
> have to use
> the RuntimeConfigurable to get enough information.
>
> Currently I'd like to display in the graph some information on
> conditionnal targets (with a if or unless attribute). The
> information is
> here since the target class has ifCondition and
> unlessCondition attributes
> but I cannot get it since the are no getter for them.
>
> So I'm wondering if using the Ant API as I do to peek into a
> project is
> something which is ok albeit the API is currently lacking a
> few things or
> the API should not be used the way I do?
>
> Cheers
>
> Christophe
>
> --
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
|