From 47c0e611b1dd7f9ea5e49b5dd3714ec5351eced6 Mon Sep 17 00:00:00 2001 From: Phil Hagelberg Date: Tue, 10 Aug 2010 20:21:19 -0700 Subject: [PATCH] Explain why clojure-test-mode is generally nicer than lein test. --- TUTORIAL.md | 7 +++++++ src/leiningen/core.clj | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/TUTORIAL.md b/TUTORIAL.md index f362e6ae..4a6b6ec9 100644 --- a/TUTORIAL.md +++ b/TUTORIAL.md @@ -200,6 +200,13 @@ just one or two namespaces at a time: Ran 2 tests containing 10 assertions. 0 failures, 0 errors. +Because it must start a new process, lein test is not a good solution +for a development cycle that involves running the tests often. For +that you would either need to look into better editor integration (see +[clojure-test-mode](http://github.com/technomancy/clojure-mode) for +Emacs) or keep a repl open and call run-tests from there as +you work. + ## Compiling If you're lucky you'll be able to get away without doing any AOT diff --git a/src/leiningen/core.clj b/src/leiningen/core.clj index 4b75f883..9b1d7946 100644 --- a/src/leiningen/core.clj +++ b/src/leiningen/core.clj @@ -5,7 +5,7 @@ (:import [java.io File]) (:gen-class)) -(def project nil) +(def ^{:doc "For internal use only, but can't be made private."} project nil) (defn- unquote-project [args] (walk (fn [item]