Hi Sean, As far as I know, that feature never saw much use. Most people like to keep their test and main sources separate, and build tools assume this.
To bind *load-tests* during compilation, you would need to control your own build process. Basically, you would have to launch Clojure and execute a script that binds *load-tess* and then calls "compile" by hand. I don't think this is possible with Leiningen or Maven, but you could do it with Ant. I doubt it's worth the trouble. -S On Aug 29, 3:46 pm, Sean Corfield <seancorfi...@gmail.com> wrote: > I'm sure this is just me being dumb about bindings but I've been > writing tests and I saw in the docs it says you can cause deftest and > with-test to not generate tests if you bind *load-tests* to false - > for production. > > I can't quite get my head around how I would bind that variable in a > way that actually affects how files containing tests are loaded / > compiled. > > Can someone point me at a good example of a project / source code that > includes tests in source files but also has a production binding for > *load-tests* ? > > Thanx! -- 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 members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
