Completed
Details
Assignee
UnassignedUnassignedReporter
importimportApproval
ScreenedPatch
CodePriority
MinorFix versions
Details
Details
Assignee
Unassigned
UnassignedReporter
import
importApproval
Screened
Patch
Code
Priority
Fix versions
Created November 8, 2010 at 9:48 PM
Updated September 23, 2011 at 10:00 PM
Resolved September 23, 2011 at 10:00 PM
RT.baseLoader assumes Compiler.getClass.getClassLoader will return a sane value. If Clojure is placed on the bootclasspath, it will return null.
Relying on baseLoader less may be possible; it looks like the ClassLoader/getSystemResource static method may get us the access we need to the bootstrap classloader, which would solve the problem I first noticed with using RT.load with the bootstrap classloader. However, there may be other issues beyond this.
More details at http://groups.google.com/group/clojure/browse_thread/thread/16c694573bd29552
I plan on investigating this further, but I've created this ticket to explain what I've discovered so far for posterity, etc.
Note that placing Clojure on the bootclasspath cuts its startup time in half; it's a measure that Charles Nutter of the JRuby project recommends.