> * 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).
I assume this is for GUI support. Will it be a requirement? > > * tasks should have access to its own XML representation. -1 A task may not have an XML representation. It may have been created dynamically. > > * Task level if and unless attributes. -0 Not sure. Sounds nice since I see people creating targets just to control the execution of a single task but the control doesn't belong to the task, it belongs to the core, so seems wrong to make it an attribute of the task. > > * Allow tasks to find out, whether another task has completed successfully. -1 - I'm cautious about coupling tasks in that way. > > * provide failonerror like functionality to all tasks. (Provide this as an aspect?? > much like logging aspect or classloader aspect). +1 OK. So we can call the if and unless attributes an aspect as well :-) > >
