Task Writer's Guide

This document describes some conventions and idioms of the boot-o-sphere.

Note: This is a work in progress. Please feel free to edit here!

Naming Conventions

Using some standard naming conventions makes it easy for users to find and require your tasks into their projects.

Project

Tasks project group and artifact ids are generally of the form

<group-id>/boot-<task>

for instance,

adzerk/boot-cljs

Namespaces

Task projects should have a single namespace containing the task definitions. This namespace is generally named after the group and project ids. For the above example this namespace would be named:

adzerk.boot-cljs

This makes it easy for the user to require your tasks in their build.boot file without having to look up the namespace name.