jruby-maven-plugins
jruby-maven-plugins copied to clipboard
jruby
rubygems-proxy.torquebox.org is down
gem install psych
Fetching: psych-3.1.0-java.gem (100%)
jar dependencies for psych-3.1.0-java.gemspec . . .
Dec 18, 2019 4:45:23 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: I/O exception (java.net.SocketException) caught when processing request to {}->http://rubygems-proxy.torquebox.org:80: Connection reset
Dec 18, 2019 4:45:23 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: Retrying request to {}->http://rubygems-proxy.torquebox.org:80
Dec 18, 2019 4:48:20 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: I/O exception (java.net.SocketException) caught when processing request to {}->http://rubygems-proxy.torquebox.org:80: Connection reset
Dec 18, 2019 4:48:20 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
(Temporary?) workaround is to force rubygems-releases mirror in Maven's settings.xml
Something like this in ~/.m2/settings.xml
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
https://maven.apache.org/xsd/settings-1.0.0.xsd">
<mirrors>
<mirror>
<id>rubygems-releases-mirror</id>
<name>RubyGems Releases mirror</name>
<url>https://repo.maven.apache.org/maven2</url>
<mirrorOf>rubygems-releases</mirrorOf>
</mirror>
</mirrors>
</settings>
Afterwards, the regular gem install psych succeeds.
Also, when checking hairy details of org.codehaus.plexus.classworlds.launcher.Launcher dependency:copy-dependencies dependency:list execution (the Java execution point that calls the demised torquebox.org repo) confirms the flip:
[DEBUG] Using mirror rubygems-releases-mirror (https://repo.maven.apache.org/maven2) for rubygems-releases (http://rubygems-proxy.torquebox.org/releases).
Offending line is https://github.com/torquebox/jruby-maven-plugins/blob/bb80f25e856f48bb08e954daa9301b4de4eb1768/ruby-tools/src/main/java/de/saumya/mojo/ruby/gems/DefaultGemManager.java#L43
Any update here? This is preventing the build of several containers that require this to update
Any updates here? Also unable to install multiple gems via gradle
Could not GET 'http://rubygems-proxy.torquebox.org/releases/rubygems/asciidoctor-diagram/1.2.1/asciidoctor-diagram-1.2.1.gem'. Received status code 503 from server: Service Temporarily Unavailable Could not GET 'http://rubygems-proxy.torquebox.org/releases/rubygems/asciidoctor/1.5.8/asciidoctor-1.5.8.gem'. Received status code 503 from server: Service Temporarily Unavailable
✗ curl http://rubygems-proxy.torquebox.org/releases/rubygems
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>503 Service Temporarily Unavailable</title>
</head><body>
<h1>Service Temporarily Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
<hr>
<address>Apache/2.2.15 (Red Hat) Server at rubygems-proxy.torquebox.org Port 80</address>
</body></html>
@Moulick I don't have any JRuby project that is managed by Gradle, but cursory search leads to following SO post - https://stackoverflow.com/q/12522676
@Mobe91 to not stop the whole development floor, I had to advise our devs to just commit that 2mb file to their respective git repo(s) and get moving. Our other solution was to get this gem into our own private maven repo which was already configured in our gradle file, but we were unable to push that gem to our private maven.
Question: Is is even possible to push a gem file to a maven repo? if I have a pom.xml etc
I think this has been ok for a while now, I think it can be closed.
