v0.1.0: The New Task Name Syntax - Dropping 'task'

2010-01-21 00:00:00 -0800

Starting in v0.0.9, the syntax to call an Albacore task had been changed to be more Rake-like. Tasks that were previously called by initializing an object: Albacore::MSBuild.new(:build) do |msb| ... end were changed to be called by a simple naming convention: msbuildtask :build do |msb| ... end.

This new syntax greatly simplified the process of calling an Albacore task, while also introducing support for the complete rake task syntax. However, it still had an issue – namely the use of “task” at the end of every task.

Dropping The Word ‘task’

In v0.1.0, all task names have bee shortened to remove the word “task”. This means that msbuildtask is now msbuild. This change was made in order to fit just a little more into the standard Ruby conventions. You don’t typically see Ruby methods, objects, or variables being named after the type of code that they represent – which is really was the word “task” was. Rather, you see these things being named by what they represent or what they do.

The New Task List

Every Albacore task has been affected, so here is the complete list of tasks with the full name and the new, shorter syntax:

More Convention-based Ruby

As Albacore progresses and changes, we are introducing more and more of the standard Ruby idioms and conventions. While I don’t expect the task names to change again, I do expect other aspects of the Albacore syntax and API to continue to evolve. Be sure to keep an eye on the blog and the wiki for all of the latest and greatest news and changes, as time goes by.

blog comments powered by Disqus