> One solution would be to load a single file and then have that file use > add-classpath to set the classpath, but add-classpath is unreliable; > I've had problems getting it to work consistently and have been told in > #clojure that I shouldn't be using it.
Possibly the cause of the compile problem I had in my last message(s)? I'll dig around and see if I can find that thread & understand what the issue with add-classpath is. > My solution for the time being is to always launch via SLIME and > consider that method of launching it canonical, essentially deprecating > the method of launching it from the shell. But obviously this is not > ideal because for some reason not everyone uses Emacs. =) Clearly the > classpath belongs in the codebase so it can be used independently of how > the application was launched. Beyond not using emacs, if you want something that's deployable in a server environment and not just on a development box it has to run with no human intervention ala emacs bootstrapping. I realize that emacs could be configured to automatically launch the clojure app, but that seems too hokey for a real production deployment. -Greg --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
