Martin Krauskopf wrote:
> Stephen Bannasch wrote:
>
>> Where in the source code can I look to see what this command is
>> actually doing?
If you turn on detailed logging
(
http://wiki.netbeans.org/FaqRubyNBLogging70) the actual command gets
logged into the log file, the logger's name is ExternalProcessBuilder
and the line starts with "Running:".
>
> 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=126>
> So 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.
Might not be the case here, but since the gem manager starts to update
the remote gems for the preselected platform (which is the built-in
JRuby 1.1.4 by default) when opened, and does not cancel the update
process when the platform is changed, the error might be related to
another platform than the one that is currently selected. So to track
down the problem you might want to try also whether <nb
install>/ruby2/jruby-1.1.4/bin/jruby -S gem list --remote --details
works from the CLI.
Erno
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
