On 25 February 2018 at 12:01, Philos Kim <philo...@gmail.com> wrote: > I know it is not desirable but it is sometimes needed, especially in my > case. > > For example , I wrote debux ( https://github.com/philoskim/debux ) > library. I want to use it only in development, not in production. If I > 'require' debux in source code to use it in development, I have to remove > it in the source code manually in production. >
The normal solution to this is to have a development namespace and a production namespace that serve as entry points for your application. During development you load in the dev namespace, and in production the prod namespace will contain the -main function that starts your application. You can omit the development namespace and anything it requires from the production classpath when you compile the jar. -- James Reeves booleanknot.com -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
