>> the true launcher will always be the java JVM executable, and I'm >> not sure this is something we should really try and hide.
I think it should be hidden, at least for newbies. Maven hides it - I invoke 'mvn' and have no idea how it invokes java. I don't know what jars it puts in the classpath, etc., and I don't need to know. Lein hides it too and I like that. Ideally a clojure installation package would include lein and a launcher that utilized lein for clojure-contrib.jar etc. Steve On Wed, Jun 30, 2010 at 4:17 PM, Rick Moynihan <rick.moyni...@gmail.com>wrote: > On 30 June 2010 21:14, Brian Schlining <bschlin...@gmail.com> wrote: > >> > >> > > >> > May I propose as a possible remedy CLOJURE_HOME. CLOJURE_HOME is the > >> > absolute path of a directory containing clojure.jar and possibly > >> > clojure-contrib.jar. Scripts should check if it's defined and use it > instead > >> > of hard-coded paths, as an example, here's my clj script (in newLISP): > >> > >> On the face of it this seems like a good idea, however it doesn't > >> really fit with the models used by tools such as leiningen, mvn or the > >> JVM. At best a CLOJURE_HOME initiative can only expect to work within > >> its own world of clj scripts etc. > > > > I can't speak for leiningen but many (most?) launcher script in the Java > > world use this as a standard convention. If you look through the launcher > > scripts for maven, groovy, scala, ant, etc you will see environment > > variables JAVA_HOME, M2_HOME (for Maven 2), GROOVY_HOME, SCALA_HOME and > > ANT_HOME. > > This is true. And I agree that where scripts are used this technique > can be useful. And in this regard it's a good convention. > > However, I don't see it helping newcomers to Clojure significantly, as > the classpath issues people face are the deeper issue. Also teaching > newcomers that this is the convention isn't really true, as tools like > Lieningen or maven don't really fit with this approach as they treat > the clojure platform as just another library dependency. > > Clojure doesn't yet have a standard launch script. In the past I've > argued that it'd be nice if it had one, though I now feel lein/mvn are > better tools for this job. That said, having a clj launch script can > be useful, and might ease the out of box experience, but again the > true launcher will always be the java JVM executable, and I'm not sure > this is something we should really try and hide. > > 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<clojure%2bunsubscr...@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 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
