On Wed, Jan 19, 2011 at 8:56 PM, Peter Niederwieser <[email protected]>wrote:
> > Dump of my brainstorming session: > > First style: untyped, general-purpose, free-form, ad-hoc > Second style: typed, special-purpose, specialized > Third style: predefined, standard, default, implicit, plugin-provided > I'm not sure whether I like the term untyped. In the courses I make a strong point that all tasks have a type and thus an API. And that tasks where you don't specify the type have a default type. Typed task do not need necessarily be special purpose. People might introduce a non-default general purpose task type with a property let's say called timer. I think the big difference is whether task types have a default action or not. This is what makes them special purpose or general purpose. I like the terminology special vs general purpose. For the third type I like the term standard tasks. It expresses the fact that plugins can standardize the build for a certain domain aspect. It makes it clearer to people that Gradle is also about standardization. Cheers Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleorg CEO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz > > Cheers, > Peter > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/some-task-terminology-tp3347273p3348427.html > Sent from the gradle-dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
