nexus.onebusaway.org is down, substituting download.osgeo.com allows OpenTripPlanner to build

[ed-g]

maven for OpenTripPlanner doesn't find some dependencies because nexus.onebusaway.org is down.

I substituted

<url>http://nexus.onebusaway.org/content/repositories/releases/</url>

with

<url>http://download.osgeo.org/webdav/geotools/</url>

In pom.xml

And OTP now builds.

[barbeau]

@ed-g Thanks for the report. We've had some intermittent issues with nexus.onebusaway.org, and I've re-opened the ticket for this at OneBusAway/onebusaway-application-modules#93.

[barbeau]

nexus.onebusaway.org should be back up now. As indicated on the OBA issue, we're looking at some options to move it to a more stable environment.

[robludwig]

It appears that this problem has resurfaced. @ed-g 's solution still applies. It looks like OneBusAway is in the process of moving the repo over to a working server

[barbeau]

@robludwig You're correct, we're in the processing of moving the maven repo. If you need OBA-specific artifacts in the mean time, the temporary location http://developer.onebusaway.org/content/ should have them.

[robludwig]

@barbeau would it make sense to (temporarily) patch the pom.xml file so that a user can clone the repo and have it build? this way the versions tagged stable (esp. 0.11.x) can remain stable while the repo is being moved over?

If so, I can quickly submit the patch.

[barbeau]

@robludwig If you're talking about patching the OTP pom.xml, @abyrd or one of the other key OTP developers would need to weigh in on that. I don't know the exact timeline for bringing nexus.onebusaway.org back up (I'm not intimately involved with that server), but I believe it should happen within the next two weeks.

On a related topic - I'm not sure of all the dependencies currently being used in 0.11 tag and newer branches, but it may be possible to get rid of the OBA maven repo reference entirely. I recently noticed that the OBA project was using the OBA maven repo as a reference for JTS, which should be referenced in Maven Central instead. It's possible that earlier in the life of the project (OTP and OBA) JTS, and maybe other artifacts, weren't available in Maven Central, which is why they ended up being hosted in the OBA Maven repo. If you can do a fresh build by just switching the maven repo URL to http://download.osgeo.org/webdav/geotools/, my suspicion is that the OBA dependency could be eliminated (at least for that branch).

[robludwig]

Thanks for the input-- that's helpful to know about the OBA repository.

My main concern is that I have an architecture that requires me to re-clone and re-install OTP on new VMs with some frequency. With the OBA repository down, it's not longer possible simply to git clone the stable 0.11.x release and then mvn package. I definitely think that as long as the repository is down, the pom.xml file should be edited so that a newcomer to the project can follow the intended clone --> package workflow.

As for possibly removing the OBA dependency, I've already done that locally so I can attest that it would work were the maintainers to choose to do that, but I don't have other thoughts.

[barbeau]

@robludwig I'd suggest going ahead and submitting a PR that patches the OTP release branches that you're concerned with (e.g., 0.11.x). That way @abyrd and others can review and easily merge the change, if they choose to do so.

[abyrd]

Confirmed that OTP will now build without the OBA repository. The OBA artifacts are available on Maven central. I will patch 0.10.x, 0.11.x, and master.

[abyrd]

Patched on all three branches. Closing.

[barbeau]

Thanks @abyrd!