Dealing with JRuby and jars
evan at phx.io
Tue Jan 17 21:17:54 EST 2012
Evan Phoenix // evan at phx.io
On Tuesday, January 17, 2012 at 5:51 PM, Eric Hodel wrote:
> On Jan 12, 2012, at 10:29 AM, Luis Lavena wrote:
> > On Thu, Jan 12, 2012 at 3:11 PM, Charles Oliver Nutter
> > <headius at headius.com (mailto:headius at headius.com)> wrote:
> > > We want the external libraries to be fully functional gems. JRuby
> > > already supports installing them like this (I know colons are bad,
> > > we'll figure out something else):
> > >
> > > gem install mvn:org.clojure:clojure
> > So what you're suggesting, even you stated differently is that you
> > want to pollute rubygems.org (http://rubygems.org) with maven artifacts wrapped as gems?
> The following line is:
> > > This creates a gem on the fly and installs it, and any scripts, tools,
> > > etc that use RubyGems see it as just another gem.
> So I take this to mean that the clojure gem only exists on the user's machine while installed and not on rubygems.org (http://rubygems.org) nor anywhere else.
Yes, thats correct. It works similar to how bundler synthesizes specs for git repos and raw directories.
> RubyGems-Developers mailing list
> RubyGems-Developers at rubyforge.org (mailto:RubyGems-Developers at rubyforge.org)
More information about the RubyGems-Developers