You can avoid conflicts. The ns you start executing in dev may exist only
on the dev source-paths, and when it configures the rest of your program
(putting functions in closure and whatnot) it can do so drawing from stuff
that's only going to be available in the dev profile. Then when you build
So, this seems to work pretty easily, though I'm relying on 'require'
resolving references in the same order as the directories in :source-paths.
For :source-paths ["src-dev", "src"], it will find
src-dev/foo/instrument.clj,instead of src/foo/instrument.clj, when both
exist.
I can't find anyth
In a nutshell: leverage distinct classpaths. Adjust the :dev profile in
project.clj to prepend a directory other than src to :source-paths, and
likewise a directory other than resources for :resource-paths. In
development, use code or resources from the dev classpath to override
default behav
How do you instrument code, e.g. apply ring wrap-reload,
wrap-stacktrace-web, etc., only in dev, not in uberjar?
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new me
