JOSM Nexus is down

[taylor.smock]

Running ant dist in buildings_tools gave the following output:

Buildfile: /Users/tsmock/workspace/josm/plugins/buildings_tools/build.xml

init:

pre-compile:

download-ivy:
      [get] Getting: https://josm.openstreetmap.de/nexus/content/repositories/public/org/apache/ivy/ivy/2.5.0/ivy-2.5.0.jar
      [get] To: /Users/tsmock/.ant/lib/ivy.jar
      [get] Error opening connection java.io.IOException: Server returned HTTP response code: 503 for URL: https://josm.openstreetmap.de/nexus/content/repositories/public/org/apache/ivy/ivy/2.5.0/ivy-2.5.0.jar
      [get] Error opening connection java.io.IOException: Server returned HTTP response code: 503 for URL: https://josm.openstreetmap.de/nexus/content/repositories/public/org/apache/ivy/ivy/2.5.0/ivy-2.5.0.jar
      [get] Error opening connection java.io.IOException: Server returned HTTP response code: 503 for URL: https://josm.openstreetmap.de/nexus/content/repositories/public/org/apache/ivy/ivy/2.5.0/ivy-2.5.0.jar
      [get] Can't get https://josm.openstreetmap.de/nexus/content/repositories/public/org/apache/ivy/ivy/2.5.0/ivy-2.5.0.jar to /Users/tsmock/.ant/lib/ivy.jar

BUILD FAILED
/Users/tsmock/workspace/josm/plugins/build-common.xml:733: Can't get https://josm.openstreetmap.de/nexus/content/repositories/public/org/apache/ivy/ivy/2.5.0/ivy-2.5.0.jar to /Users/tsmock/.ant/lib/ivy.jar

This is probably due to the outage ​today. I'm guessing that the Nexus isn't automatically getting started on server restart.

Workaround:

plugins/build-common.xml

@@ -728 +728 @@
     -->
     <target name="download-ivy">
         <mkdir dir="${ivy.jar.dir}"/>
-        <get src="https://josm.openstreetmap.de/nexus/content/repositories/public/org/apache/ivy/ivy/${ivy.version}/ivy-${ivy.version}.jar"
+        <get src="https://repo1.maven.org/maven2/org/apache/ivy/ivy/${ivy.version}/ivy-${ivy.version}.jar"
              dest="${ivy.jar.file}"
              usetimestamp="true"/>
     </target>

[stoecker]

Bah. SysV init script and not properly including runlevel specs. Fixed and started.

[taylor.smock]

Bah. SysV init script and not properly including runlevel specs. Fixed and started.

Stuff happens. :(
At least it is something that was not OSM user facing. Just developer facing.