Dealing with JRuby and jars
nick at quaran.to
Tue Jan 17 19:18:59 EST 2012
I'll be honest, I don't remember why we added this. I think it was
basically to ensure that gems that could be pushed could *always* be
I'm suprised metadata hasn't been brought up here. It would solve this
entire problem and let jruby gems specify whatever they want.
On Thu, Jan 12, 2012 at 1:46 PM, Evan Phoenix <evan at phx.io> wrote:
> I feel like the crux of the request, removing the dependency name check on
> push, has gotten lost in the discussion.
> Given that it currently doesn't provide a true safeguard that the gem's
> deps are actually satisfied by gems currently on rubygems.org, I think we
> should go ahead and simply remove the check all together.
> If users create gems that have unresolvable deps (something they can
> easily do now) thats on them to do. We don't have a reason to police this
> aspect of gem availability.
> Any thoughts?
> Evan Phoenix // evan at phx.io
> RubyGems-Developers mailing list
> RubyGems-Developers at rubyforge.org
More information about the RubyGems-Developers