Just another 2¢ in case someone stumbles across this thread from a search…
I've actually seen oddities like this on OpenSolaris and my Mac, too, when running from a jar: I'm a little hazy on the details (working late is not good for the memory!) but IIRC there was some unhappy interaction between the jar's Class-Path manifest entry and the command-line classpath (if there was one). One of the symptoms was that my jar would start to load, and I'd get a stack trace which reported the gen-classed class not found. (Very confusing, given that javap would happily print it for me!) Nowhere in the stack trace was the *real* cause, which was that one of the classes or interfaces that my class required wasn't in the run- time classpath. Particularly in the case of the servlets I'm building, the jar has to have a Class-Path entry to find the non-standard libraries it needs. I sometimes feel like half of my Java development time is spent debugging classpath problems! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
