Short answer: never execute code at the top-level of your source files. Only define functions.
If you have a shared constant that only needs to be evaluated once, consider using delay/force. -S On Aug 7, 4:46 am, Christian Schuhegger <christian.schuheg...@gmail.com> wrote: > Hi all, > > I just had a lengthy debugging session behind me to find out why maven > hangs when trying to execute the "clojure:compile" target of the > clojure-maven-plugin. > > I found out that the problem does not lie in maven but in clojure (or > in my code if you want to see it that way). My code executes some > expressions that cause the clojure thread pools to be started. These > thread pools stay alive after the compilation phase is over. My intent > would be that such objects are only created when running the program > but not when compiling it. > > The only reference where I found this problem discussed is from > 2009-06-01:http://code.google.com/p/clojure/issues/detail?id=120 > but I did not find any follow up or recommendation on how to deal with > such issues? > > What is the current recommended way on how to deal with this > situation? > > Many thanks, > Christian -- 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
