yogsototh/leiningen
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clarify checkout dependency FAQ.

Browse source
This commit is contained in:
Phil Hagelberg 2010-12-02 18:10:17 -08:00
parent baf1083dd4
commit 10ef6f7323
1 changed files with 9 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
README.md
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.
**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
symlink some other projects into it, Leiningen will allow you to
hack on them in parallel. That means changes in the dependency will
be visible in the main project without having to go through the
whole install/switch-projects/deps/restart-swank cycle.
**A:** Use a feature called _checkout dependencies_. If you create a
directory called <tt>checkouts</tt> in your project root and symlink
some other project roots into it, Leiningen will allow you to hack
on them in parallel. That means changes in the dependency will be
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?
**A:** Yes. Some libraries, such as log4j, depend on projects that are