julienfantin · November 17, 2013 01:44
diff --git a/leinrc b/leinrc
 LEIN_JAVA_CMD=${LEIN_JAVA_CMD-drip}
diff --git a/profiles.clj b/profiles.clj
 {:user {:plugins [;; Is this still needed or built-in now?
                  [lein-pprint "1.1.2-SNAPSHOT"]

                  ;; Pretty cool for messing around with a library
                  ;; without setting anything up, it'll put you in a
                  ;; repl when you `lein try some-lib-name`. Doesn't
                  ;; play well with emacs though, being that it won't
                  ;; run headless and let you connect to it...
                  [lein-try "0.4.1"]

                  ;; You know you want it :)
                  [lein-typed "0.3.1"]

                  ;; This will let you interactively upgrade to more
                  ;; recent versions of your project's dependencies.
                  ;; lein ancient upgrade :interactive
                  [lein-ancient "0.5.2"]

                  ;; Not quite sure about this one... Should work OOTB.
                  [lein-autoreload "0.1.0"]

                  ;; Saves you from embedding a jetty instance inside
                  ;; your app code, which usually doesn't play well with
                  ;; any real-world deployment option -- and can start a
                  ;; repl which is that much less configuration to deal
                  ;; with... Also haven't found another way to build a
                  ;; war file!
                  [lein-ring "0.8.8"]

                  ;; Midje is a much better way to run even vanilla
                  ;; core.test files. It will autotest from the shel
                  ;; with lein midje :autotest, and from the repl which
                  ;; is much faster, and font-locked in emacs.  Just
                  ;; (use 'midje.repl) then (autotest)
                  [lein-midje "3.1.1"]]

        :dependencies [;; Slamhound will figure out how to rewrite your
                       ;; ns declarations, emacs integration available.
                       [slamhound "1.3.3"]

                       ;; Required dependency even for lein midje only
                       [midje "1.5.1"]]
        }}
	{:user {:plugins [;; Is this still needed or built-in now?
	[lein-pprint "1.1.2-SNAPSHOT"]

	;; Pretty cool for messing around with a library
	;; without setting anything up, it'll put you in a
	;; repl when you `lein try some-lib-name`. Doesn't
	;; play well with emacs though, being that it won't
	;; run headless and let you connect to it...
	[lein-try "0.4.1"]

	;; You know you want it :)
	[lein-typed "0.3.1"]

	;; This will let you interactively upgrade to more
	;; recent versions of your project's dependencies.
	;; lein ancient upgrade :interactive
	[lein-ancient "0.5.2"]

	;; Not quite sure about this one... Should work OOTB.
	[lein-autoreload "0.1.0"]

	;; Saves you from embedding a jetty instance inside
	;; your app code, which usually doesn't play well with
	;; any real-world deployment option -- and can start a
	;; repl which is that much less configuration to deal
	;; with... Also haven't found another way to build a
	;; war file!
	[lein-ring "0.8.8"]

	;; Midje is a much better way to run even vanilla
	;; core.test files. It will autotest from the shel
	;; with lein midje :autotest, and from the repl which
	;; is much faster, and font-locked in emacs. Just
	;; (use 'midje.repl) then (autotest)
	[lein-midje "3.1.1"]]

	:dependencies [;; Slamhound will figure out how to rewrite your
	;; ns declarations, emacs integration available.
	[slamhound "1.3.3"]

	;; Required dependency even for lein midje only
	[midje "1.5.1"]]
	}}
No results found