Re: Problem with CLASSPATH

2009-04-20 Thread Adam Blinkinsop
On Apr 5, 1:32 pm, dlb wrote: > I have the same problem on my Mac as well, i.e. if clojure.jar is > loaded from ~/Library/Java/Extensions rather than from the classpath, > then clojure does not find files on the classpath.  I did some poking > around and on my Mac OS X 10.5.6 with Java 6. > ...

Re: Problem with CLASSPATH

2009-04-05 Thread dlb
I have the same problem on my Mac as well, i.e. if clojure.jar is loaded from ~/Library/Java/Extensions rather than from the classpath, then clojure does not find files on the classpath. I did some poking around and on my Mac OS X 10.5.6 with Java 6. When I start clojure with clojure.jar only o

Re: Problem with CLASSPATH

2009-03-24 Thread Rich
I think I figured it out. If I install clojure.jar into /Library/Java/Extensions/ (the ext directory on Macs) then it won't work. Even if I use java -cp ... to point to a different clojure.jar. Simply having the jar in that folder breaks things. Once I deleted it from /Library/Java/Extensions, I

Re: Problem with CLASSPATH

2009-03-24 Thread Stephen C. Gilardi
On Mar 24, 2009, at 10:49 AM, Mark Volkmann wrote: On Tue, Mar 24, 2009 at 9:44 AM, Stephen C. Gilardi wrote: One thing to note is that namespace names should always have at least one period in them. I believe this is due to a rule regarding Java packages. At some point the "clojure" name

Re: Problem with CLASSPATH

2009-03-24 Thread Mark Volkmann
On Tue, Mar 24, 2009 at 9:44 AM, Stephen C. Gilardi wrote: > > One thing to note is that namespace names should always have at least one > period in them. I believe this is due to a rule regarding Java packages. At > some point the "clojure" namespace became "clojure.core" for this reason. I > ha

Re: Problem with CLASSPATH

2009-03-24 Thread Mark Volkmann
On Tue, Mar 24, 2009 at 9:44 AM, Stephen C. Gilardi wrote: > > One thing to note is that namespace names should always have at least one > period in them. I believe this is due to a rule regarding Java packages. At > some point the "clojure" namespace became "clojure.core" for this reason. I > ha

Re: Problem with CLASSPATH

2009-03-24 Thread Stephen C. Gilardi
On Mar 24, 2009, at 5:03 AM, Rich wrote: Has anyone gotten 20090320 to work on a new MacBook Pro running Leopard? I tried it just now and it worked for me. Here's the test I did: - Download 20090320 zip file - Expand it into dir - create a file in dir called Structure.clj wi

Re: Problem with CLASSPATH

2009-03-24 Thread David Nolen
The latest version of Clojure incorporated lazy sequences which broke many libraries early on. Most of these problems have been worked out. In my experience you should use the cutting edge version of everything including SLIME. I clone everything from GitHub (clojure, clojure-contrib, swank-cloju

Re: Problem with CLASSPATH

2009-03-24 Thread Rich
Has anyone gotten 20090320 to work on a new MacBook Pro running Leopard? With further investigation, it looks like any call to (use...) either explicitly or as part of an (ns...) function call causes clojure to crash since the upgrade. I've fiddled around with the class path, and nothing seems to

Re: Problem with CLASSPATH

2009-03-23 Thread Rich
Let me clarify my last post. In both cases, the directory was on the class path (either implicitly as ".", or explicitly given the absolute path). However, in both cases I got the same FileNotFound exception. -Rich- On Mar 23, 6:39 am, Rich wrote: > "." should be set by default. I verified tha

Re: Problem with CLASSPATH

2009-03-23 Thread Rich
"." should be set by default. I verified that it was set using (. System getProperties). I also tried explicitly setting the absolute path using -cp. No luck on either count. -Rich- On Mar 23, 5:14 am, revoltingdevelopment wrote: > I also had the NO_SOURCE_FILE error when using contrib packages

Re: Problem with CLASSPATH

2009-03-23 Thread revoltingdevelopment
I also had the NO_SOURCE_FILE error when using contrib packages, upon upgrade to 20090320. My CLASSPATH included ".". I had to revert to starting clojure with an explicit -cp. I'm new to both Java and Clojure, but this led me to think my CLASSPATH was being ignored. I chalked it up to my misun

Re: Problem with CLASSPATH

2009-03-23 Thread Mark Volkmann
On Mon, Mar 23, 2009 at 7:34 AM, Rich wrote: > > Structure.clj does call ns as shown below: > > (ns Structure) > > So, as far as I can tell, Clojure should look for Structure.clj in the > class path. At least, that's what it used to do. I guess I could move > all the code into a sub-directory, an

Re: Problem with CLASSPATH

2009-03-23 Thread Rich
Structure.clj does call ns as shown below: (ns Structure) So, as far as I can tell, Clojure should look for Structure.clj in the class path. At least, that's what it used to do. I guess I could move all the code into a sub-directory, and rename all the namespaces--but I'd rather keep it organize

Re: Problem with CLASSPATH

2009-03-23 Thread Mark Volkmann
On Mon, Mar 23, 2009 at 4:59 AM, Rich wrote: > > Hi, > > I'd been using the 20081217 release. The following code worked, as > long as Structure was in the working directory: > > Clojure > user=> (use 'Structure) > nil > > However, after I updated to 20090320, I get the following errors: > > Cloju