On 7/12/06, Charles O Nutter <[EMAIL PROTECTED]> wrote:
What you're suggesting is basically what I'm hoping to do, except that I think we could just have the load path explicitly contain all jars on the classpath, so that when you do a load it will search classpath jars as well. That part's not too difficult...what's difficult is then allowing that resource location, ultimately a resource URL, to be File.open'ed like a normal java.io.File (albeit a read-only one). We have many layers of abstractions that depend on Ruby File being a File, along with some nio stuff.
Actually what you're suggesting may be better in some ways since it would give us a load path element that means "now search classloader resources". My version would not work if additional jars were loaded at runtime, such as within an application server.
I wouldn't foresee any issues putting some "magic" load path element in based on jruby.home.
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ www.jruby.org
Application Architect @ www.ventera.com
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Jruby-devel mailing list Jruby-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jruby-devel
