Hans Dockter schrieb:
[...]
Introducing the notion of public and private tasks would be a way to
find related groups. It is an interesting idea. On the other hand there
might be also a set of callable tasks that form a group you might want
to skip, where this approach would not work.
that depends on how the information what to skip is propagated..
assuming you have a list of tasks and you start skipping the public
tasks that are marked to be skipped and skipp allthe private tasks these
public tasks do depend on, then I see no problem with that idea. The
curcial part here is how to say soemthing is public/callable and not,
and what should be skipped. But the later is always an issue to solve I
guess.
An alternative would be to introduce the concept of task groups. Each
task can belong to 0..n task groups and we allow to skip specific
tasks or task groups.
not sure, but that sounds a bit complicated to me
The question is if it will work to find skip groups implicitly. I'm a
bit skeptical about this. The alternative is to leave it to the user to
decide which tasks belong to particular groups.
I think letting the user to do too much declartion work should be
avoided if possible. So if there is a solution that allows implicit
grouping, then "we" should have a close look at it.
bye blackdrag
--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
