-
-
Notifications
You must be signed in to change notification settings - Fork 180
Task Writer's Guide
Micha Niskin edited this page Dec 28, 2014
·
19 revisions
This document describes some conventions and idioms of the boot-o-sphere.
Using some standard naming conventions makes it easy for users to find and require your tasks into their projects.
Tasks project group and artifact ids are generally of the form
<group-id>/boot-<task>
for instance,
adzerk/boot-cljs
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
.
You can find other developers and users in the #hoplon
channel on freenode IRC or the boot slack channel.
If you have questions or need help, please visit the Discourse site.
- Environments
- Boot environment
- Java environment
- Tasks
- Built-ins
- Third-party
- Tasks Options
- Filesets
- Target Directory
- Pods
- Boot Exceptions
- Configuring Boot
- Updating Boot
- Setting Clojure version
- JVM Options
- S3 Repositories
- Scripts
- Task Writer's Guide
- Require inside Tasks
- Boot for Leiningen Users
- Boot in Leiningen Projects
- Repl reloading
- Repository Credentials and Deploying
- Snippets
- Troubleshooting
- FAQ
- API docs
- Core
- Pod
- Util