2009/9/10 Phil Hagelberg <p...@hagelb.org>: > > Rick Moynihan <rick.moyni...@gmail.com> writes: >> This issue has got me thinking that the real problem appears to be >> that there isn't a standard or default way (script) to start up and >> run java/clojure projects... i.e. though this solves the problem when >> running clojure programs in emacs it doesn't do so for when you move >> into a different environment (perhaps staging or production) and want >> to run a REPL configured for your project or clojure program. > > Strongly agreed. Clojure would be much more approachable and obvious > if > it included a standard shell script.
Glad I'm not the only one :-) >> Personally I think finding a nice lightweight, default solution to >> this problem that can be supported by all environments/editors/IDE's >> would make clojure even more suited to rapid prototyping, experimental >> development and bootstrapping projects in a painless manner. > > I know there's one included in contrib now, but it's not quite the > same. I suppose in order to be portable there'd need to be a batch > file > for windows too; it's a shame there's no good cross-platform way to > handle > that. > > -Phil As I'm sure you and many others know, this problem exists in the Java community also... A few years ago I found a solution in Apache Commons Launcher: http://commons.apache.org/launcher/ It uses a lot of the infrastructure from ant and is pretty powerful, providing a cross platform way of specifying jvm args, classpaths, library paths etc... Sadly the project is largely moribund but other than being poorly documented it worked pretty well... I could imagine a pure clojure implementation of this (perhaps based on lancet?) that would use a clojure DSL instead of ant xml to configure the VM in a cross platform manner. The only problem I ran into with commons launcher was to do with System.in being passed through the VMs... It worked but its implementation was inefficient and resulted in excessive CPU consumption unless you switched it off... This was an easy work around for me, as I didn't need to read from System.in, but I can imagine it being a problem if you're running a REPL. I suspect however that it was just a bug, rather than a larger design flaw. R. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
