Intermittent failures to download maven dependencies

[barbeau]

Starting around May 24th there appeared to have been intermittent issues with downloading maven artifacts from the nexus.onebusaway.org maven repository (which contains all previous releases of OBA, as well as dependencies required to build the project).

According to @alanborning, @bdferris is working on updating the machines hosting the artifacts.

As of 6/10, it appears that nexus has been migrated to a new machine (when you hit nexus.onebusaway.org from a browser, it now shows a different page), and some artifacts are available to download.

However, it appears that we're missing at least two artifacts from the nexus repo, which results in a broken build on a machine that hasn't previously built OBA (i.e., a machine that hasn't previously cached these artifacts).

If you run mvn clean install -U on a new machine, you get this error:

[INFO] onebusaway-quickstart-assembly .................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 31.737 s
[INFO] Finished at: 2014-06-05T15:10:48-05:00
[INFO] Final Memory: 29M/623M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project onebusaway-geospatial: Could not resol
ve dependencies for project org.onebusaway:onebusaway-geospatial:jar:1.1.12-SNAP
SHOT: The following artifacts could not be resolved: com.vividsolutions:jts:jar:
1.10, edu.washington.cs.rse:javaproj:jar:1.0.4: Could not find artifact com.vivi
dsolutions:jts:jar:1.10 in public.onebusaway.org (http://nexus.onebusaway.org/co
ntent/groups/public/) -> [Help 1]

Therefore, it appears that com.vividsolutions:jts:jar:1.10 and edu.washington.cs.rse:javaproj:jar:1.0.4 are the two missing artifacts. JTS 1.10 isn't available from Maven Central for some reason, and Javaproj by UW doesn't seem to be publicly available for download elsewhere, so users without a cached Maven repo can't build OBA.

A manual workaround is described here (to manually download a zip file containing these artifacts, pulled from my local machine, and install them yourself):
https://groups.google.com/d/msg/onebusaway-developers/OvI7qWOinME/Ouz2YMUAc-wJ

Discussions on the OBA users and dev lists about this issue:
https://groups.google.com/d/msg/onebusaway-developers/OvI7qWOinME/07pZlbG4RCEJ
https://groups.google.com/d/msg/onebusaway-users/mAxn6kednRI/DD61EAqCZC0J

[bdferris]

We were in the process of migrating to a new Nexus instance on a new UW server, but that work wasn't completed yet. Unfortunately, it looks like someone switched the DNS entry prematurely. I will see if someone can switch it back?

[barbeau]

@bdferris Thanks for taking a look at this!

Another workaround - @sheldonabrown has set up a maven repo hosting some of the missing artifacts, so you can now grab missing artifacts from Sheldon's repo using the following maven command format (vs. the manual method mentioned in the above lists):

mvn org.apache.maven.plugins:maven-dependency-plugin:2.1:get -DrepoUrl=http://developer.onebusaway.org/archiva/repository/internal/ -Dartifact=com.vividsolutions:jts:1.10

This should pull down the artifact from Sheldon's repo if nexus isn't up, and install it in your local maven repository. If you keep getting missing artifact errors for new artifacts, repeat the above maven command for each of them, and you should eventually get to a complete build.

[barbeau]

From S. Morris Rose:
https://groups.google.com/d/msg/onebusaway-developers/OvI7qWOinME/tEW-pEUIfVgJ

I think that our Maven nightmare is over- it evidently was due to a machine being restarted with configuration that gave it the same IP as the box serving nexus.cs. My mistake- made back in December 2013 but laying in wait until late May. Sorry for the outage- it seemed to come and go, which made it a head-scratcher.

It seems fixed to me (i.e., I was able to do a complete build from scratch, and the nexus.onebusaway.org has been correctly pointing to the Sonatype repo for the last day or so), so I'm going to close this issue.

[barbeau]

Looks like nexus.onebusaway.org is down again, but this time isn't responding at all - reported at opentripplanner/OpenTripPlanner#1463

[barbeau]

To update everyone - there is a temporary fix in place that makes the existing mvn repo hosted at UW functional, so I'm going to close this issue. We're looking at moving this to a virtualized server at USF for long-term stability.

[barbeau]

Looks like this is an issue again - nexus.onebusaway.org is currently timing out.

Reported by new user on the mailing lists:
https://groups.google.com/forum/#!topic/onebusaway-developers/bagZPozXR68
https://groups.google.com/forum/#!topic/onebusaway-developers/DEl0nZl_8fk

[smrose]

It's back. That service went out when our building lost cooling on 6 October. Today I requested that it be brought back up, and that seems to have succeeded.