From: Charles Oliver Nutter <headius@...>
Date: 2010-06-30T18:41:25+09:00
Subject: [ruby-core:30970] Re: [Feature #1478] Ruby archive

JRuby already supports loading scripts out of .jar files, either by
first requiring the jar file and then requiring files inside it, by
adding the jar file to the load path, or by adding the jar file to the
Java classpath. It's also possible to load out of a jar URL, even
remotely:

require 'http://blah.com/my.jar!/somefile.rb'

I'd be happy to provide a longer description of how JRuby supports
archives. I believe we have the most complete support, and people are
using these features constantly in JRuby already. It would be "very
good" if the new archive format didn't introduce something totally
different.

- Charlie

On Wed, Jun 2, 2010 at 9:36 PM, NAKAMURA, Hiroshi <nakahiro@gmail.com> wrote:
> Hi,
>
> Sorry for late response. ��I hope my comment doesn't have bad effects
> to your RSoC project by any chance.
>
> On Fri, May 21, 2010 at 14:29, Jonathan Nielsen <jonathan@jmnet.us> wrote:
>> I am actually here, and I would be very interested in hearing from
>> community members about this. ��I am somewhat confused by your comment
>> here. ��I don't think that simply taking the jar/zip format and
>> slapping ruby files into it is in any way adequate for the project at
>> hand. ��Could you clarify your opinion about this? ��Thank you.
>
> It's good if the archive works transparently from the current
> 'feature' system of Ruby I think. ��Scanning archives and 'require'
> customization would be enough challenging task. ��Please consider to
> not adding 'require_from_archive' or something new method that breaks
> source code compatibility.
>
> Regards,
> // NaHi
>
>