ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <>
Subject Re: [DISC] Task API
Date Mon, 26 Mar 2001 08:36:07 GMT
At 09:59  26/3/01 +0200, Stefan Bodewig wrote:
>* tasks provide some way to identify their attributes from the
>  outside. 
>  Possible solutions include a special method like getProperties(), an
>  external describing file shipping with the task class or special
>  javadoc comments parsed by a custom doclet. Whatever the method it
>  should not impose any cost on runtime as it is only used a small 
>  proportion of the time (design-time).  

+1 but not a high priority except for integration into GUIS.

>* tasks should have access to its own XML representation.

The tasks should have the option of accessing it but 90% of time should not
(except for nested task hierarchies).

>* Task level if and unless attributes.

-1 if built into tasks
+0 if supplied as a aspect in different namespace

>* Allow tasks to find out, whether another task has completed successfully.

>* provide failonerror like functionality to all tasks. (Provide this as an
>  much like logging aspect or classloader aspect).

+1 if as aspect, 
-1 if built into base task



| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |

View raw message