-
-
Notifications
You must be signed in to change notification settings - Fork 180
Boot for Leiningen Users
micha edited this page Dec 25, 2014
·
21 revisions
All of the different abstractions used to control how Leiningen works ([plugins], profiles, middleware, and injections)
The equivalent of Leiningen profiles and middleware in boot are tasks that modify the environment and return clojure.core/identity
, the no-op task middleware.
For example, a task to add the test
directory to the :source-paths
when running tests, similar to the test
profile in Leiningen:
(deftask testing
"Profile setup for running tests."
[]
(set-env! :source-paths #(conj % "test"))
identity)
Profiles are "activated" simply by adding them to the pipeline, for example:
$ boot testing run-tests
This is equivalent to Lein's
$ lein with-profile testing run-tests
The equivalent of lein pprint
in boot is:
boot show -e
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