Ken Wesson <[email protected]> writes:
>> For example, take this use-case of modules A, B, C and D:
>>
>> A --> B --> C
>> `-> D
>>
>> (A depends on B and D, B depends on C)
>>
>> Write a shell script ...
>
> And this is how leiningen making users jump through hoops to do fairly
> simple builds with local dependencies *itself* can encourage "works on
> my machine" builds. :) Which is preferable from that stand point,
> after all: a leiningen build script or lots of idiosyncratic shell
> scripts?
Off the top of my head:
(ns leiningen.sub
(:use [leiningen.core :only [apply-task task-not-found]]))
(defn sub [task-name & args]
(doseq [project (projects-in-dir)]
(apply-task task-name project args task-not-found)))
Implementation of projects-in-dir left as an exercise for the
reader. Shouldn't be more than four lines. Push the lein-subs plugin to
clojars: problem solved in a repeatable, maintainable way.
-Phil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
