On 18/06/10 2:52 PM, Steve Ebersole wrote:
I have seen mentioned a number of times the notion of a set of convention tasks such that a project using Gradle can be checked out and the developer could just know some of the tasks to call by convention. Is there a list of these somewhere?
There's a brief description of them in http://gradle.org/0.9-preview-3/docs/userguide/tutorial_java_projects.html#N10415
There's really only the following lifecycle tasks at the moment: * clean * check * assemble * build Arguably classes and test should be included in this list too.
Like for example, I have seen such a task named "doc" or "docs" a number of times and I think it would be beneficial for the jDocBook plugin (and other documentation related tasks/plugins) to register "depends on" for its tasks against that convention task.
I agree. Perhaps we should add a 'docs' task to the base plugin (and the list above), or add a documentation-base plugin which adds in 'docs' plus whatever convention properties we need for documentation.
-- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
