Hi all, On Sun, Jun 28, 2009 at 1:37 AM, Laurent PETIT <laurent.pe...@gmail.com>wrote:
> >> That's certainly why you're having problems when you mess up the > >> dependencies in places where there is a hierarchy of classloaders > >> involved : clojure-contrib was loaded with the "main classloader" > >> along with java core libraries, and clojure was loaded with a "child" > >> classloader. And thus clojure-contrib classes were not able to see any > >> of the classes in the child classloader. > > > > I see. But even this is not a problem when loading code > > from .clj files instead of .class files, which may be why > > I haven't run into it much. > > Interesting problems, since they force to think hard about all those > classloader issues :-) > > Indeed, since resource files (clj files) are probably delivered by the > same classloaders that would have delivered class files, it's weird > that it works in one case and not the other. Maybe I don't understand > the differences sufficiently precisely, after all :-$ Except that resource files don't depend on clojure.core classes. (In truth a resource file can't have dependencies.) My current understanding of the problem is that although sources on java.ext.dirs are loaded from the "root" clasloader, they are compiled and the resulting classes are loaded by a classloader which is a descendant of the classloader that loaded Clojure. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
