Clarify checkout dependency FAQ.

This commit is contained in:
Phil Hagelberg 2010-12-02 18:10:17 -08:00
parent baf1083dd4
commit 10ef6f7323

View file

@ -164,12 +164,15 @@ See the plugin task's help for more information.
if they're not worth spinning off; the plugin guide shows how. if they're not worth spinning off; the plugin guide shows how.
**Q:** I want to hack two projects in parallel, but it's annoying to switch between them. **Q:** I want to hack two projects in parallel, but it's annoying to switch between them.
**A:** Use a feature called _checkout dependencies_. If you create
a directory called <tt>checkouts</tt> in your project root and **A:** Use a feature called _checkout dependencies_. If you create a
symlink some other projects into it, Leiningen will allow you to directory called <tt>checkouts</tt> in your project root and symlink
hack on them in parallel. That means changes in the dependency will some other project roots into it, Leiningen will allow you to hack
be visible in the main project without having to go through the on them in parallel. That means changes in the dependency will be
whole install/switch-projects/deps/restart-swank cycle. visible in the main project without having to go through the whole
install/switch-projects/deps/restart-swank cycle. Note that this is
not a replacement for listing the project in :dependencies; it
simply supplements that.
**Q:** Is it possible to exclude indirect dependencies? **Q:** Is it possible to exclude indirect dependencies?
**A:** Yes. Some libraries, such as log4j, depend on projects that are **A:** Yes. Some libraries, such as log4j, depend on projects that are