Stephen Bannasch wrote:
>> Stephen Bannasch wrote:
>> [...]
>>> However I got these errors when selecting Tools:Ruby Gems -- not sure
>>> what they mean ??
>>
>> Could you try to follow:
>>
>>
http://wiki.netbeans.org/RubyGems#section-RubyGems-GemsFetchingFailed>>
>> I've just tried with JRuby trunk and it works for me. Having few days
>> old thought. Will upgrade to double-check.
>
> gem list --local --details
>
> works fine ...
This one is usually working. I rather asked for the second one noted on
the wiki page:
gem list --remote --details
and/or:
jruby -S gem list --remote --details
> The error is reported after just opening Tools:Ruby Gems
>
> The Ruby Gems dialog first reports it is "Updating" -- presumably it is
> not actually updating because I hadn't yet asked NB to do any
> modification and just opening Ruby Gems should not modify my system.
[...]
NetBeans does not do any modification. But it starts to update list of
remote gems available on remote RubyGems repository (usually from
rubyforge.org) when the Gem Manager dialog is opened.
> I opening "Ruby Gems" doing more than just:
>
> jruby -S gem list --local --details
Yes, it does also 'remote' as mentioned above.
> Where in the source code can I look to see what this command is actually
> doing?
It invokes RubyGems in the same way as one does from CLI. Sources for
RubyGems might be found at its homepage:
http://rubyforge.org/scm/?group_id=126So does the remote update work from CLI at the time it does not work
from NetBeans? Sometime it might be just temporary rubyforge.org problems.
m.
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...