Community
Participate
Working Groups
Ripplor (and probably all ruby-based tools) can retry git clone/push and publishing operations before giving up due to network issues for example.
Created attachment 206179 [details] Retry logic and repo name check
I applied this patch and hit the following problem: $ ~/eclipse/virgo/org.eclipse.virgo.web-server/scripts/ripplor/ripplor.rb -r kernel -u gnormington /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- choice (LoadError) from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' from /Users/glynnormington/eclipse/virgo/org.eclipse.virgo.web-server/scripts/ripplor/options.rb:2 from /Users/glynnormington/eclipse/virgo/org.eclipse.virgo.web-server/scripts/ripplor/ripplor.rb:6:in `require' from /Users/glynnormington/eclipse/virgo/org.eclipse.virgo.web-server/scripts/ripplor/ripplor.rb:6 I tried installing the choice and etc gems, but the problem persisted, so I stashed the changes and the ripple began normally, which indicate some problem with the patch or my ruby setup.
Flagging as an enhancement given that most people don't hit this problem and it's really a problem with certain networks.
With the introduction of virgo-root and the switch to Gradle (Bug 463462) this seems obsolete, now.