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 https://github.com/opentripplanner/OpenTripPlanner/issues/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.

[barbeau]

Thanks @smrose!

[slecorne]

It looks like nexus.onebusaway.org is down again. Got an internal 500 server error while trying to get binary snapshots: http://nexus.onebusaway.org/service/local/artifact/maven/content?r=public&g=org.onebusaway&a=onebusaway-gtfs-merge-cli&v=1.3.4-SNAPSHOT

[smrose]

Looks like the file system failed - I can't even log in. It was scheduled, as announced some time ago, to be retired in less than a week anyway. As far as I know, no plan to replace it has been forged.

On Tue, Oct 28, 2014 at 7:47 AM, slecorne [email protected] wrote:

It looks like nexus.onebusaway.org is down again. Got an internal 500 server error while trying to get binary snapshots:

http://nexus.onebusaway.org/service/local/artifact/maven/content?r=public&g=org.onebusaway&a=onebusaway-gtfs-merge-cli&v=1.3.4-SNAPSHOT

— Reply to this email directly or view it on GitHub https://github.com/OneBusAway/onebusaway-application-modules/issues/93#issuecomment-60767076 .

S. Morris Rose technical staff University of Washington CSE

[alanb2718]

To provide a bit more detail: nexus.onebusaway.org has been hosted on a really ancient machine at the University of Washington. We've been talking for months if not years about the fact that it could fail at any time and we need to move maven to a different host. To mollify our lab management (who has been bugging us about getting that machine out of the building) we said that we would decommission it Oct 31 at the latest. So it looks like All Hallow's Eve has come a couple of days early, as far as this machine is concerned.

There is a new-ish machine at UW (helsinki.cs.washington.edu) that could host it, or it could be on a new virtual server somewhere else. (The virtual server at USF turned out to be too expensive though.)

[ramunask]

Why not to place artifacts in central maven repository?

[bdferris]

We do put some of our libraries in the central maben repository (eg. onebusaway-gtfs) if we think they'll actually be used by others as build dependencies. However, the central repository isn't appropriate for snapshots produced by the CI server or for large release artifacts (the application suite, for example) that aren't really used as build dependencies. Finally, our own repo serves as a nice cache of the dependencies we do need to build OBA (at least, if you are located near Seattle ;)

[barbeau]

@bdferris I haven't looked at this closely, but when I was having issues setting up a new machine a few months ago it did seem that some of the critical build dependencies for oba-app-modules that aren't OBA-specific (e.g., com.vividsolutions:jts - see this comment) are being pulled off the OBA maven repo, instead of maven central or somewhere else non-OBA. Is this intentional/required as part of the current OBA build structure? If not, we may want to revisit some of the pom.xml files.

[bdferris]

Maybe rings some bells? Perhaps jts wasn't in the main repo back in the day but is now?

[barbeau]

That would make sense - Maven Central search is actually timing out for me right now, so I can't see if JTS is up there now :).

On the general topic of OBA artifacts - another option is JCenter. I know Android Gradle plugin artifacts moved there fairly recently, and if the Android team is doing it, it must be the right thing to do ;). Seriously, though, it seems like it is fairly OSS-friendly, although from a quick look I wasn't able to find exact quotas on size for free OSS projects (if there are quotas for OSS projects). I just pinged them to see. According to Bintray, benefits are here. Caveat - I haven't had a chance to look into all the trade-offs between Maven Central vs. JCenter, so this isn't a strong endorsement of going in that direction, just an FYI.

[barbeau]

From JCenter:

The main limits of a free account are 500MB of storage, maximum of 50MB per file, and 300 REST API calls per day.

[bdferris]

As a data point, the current size of all org/onebusaway release artifacts is in our existing Nexus repository is 9.2 GB. That includes everything we've ever released.

[barbeau]

Looks like JTS is available via Maven Central - I just opened a new ticket (https://github.com/OneBusAway/onebusaway-application-modules/issues/103) to reference the artifact there, and review others that might be available in Maven Central.

[sheldonabrown]

For those critically blocked on this, I have a backup in place now at:

http://developer.onebusaway.org/content/

This will eventually become the new server as soon as it passes testing and we make the appropriate DNS changes.

[barbeau]

Thanks @sheldonabrown!

[ed-g]

Hi everyone,

It looks like both http://developer.onebusaway.org/content/ and http://nexus.onebusaway.org/content/groups/public/ contain no dependancies.

The pom.xml from 1.1.16 which appears to be current stable branch references nexus: https://github.com/OneBusAway/onebusaway-application-modules/tree/onebusaway-application-modules-1.1.16

For me the build does not work:

Downloading: http://nexus.onebusaway.org/content/groups/public/org/onebusaway/onebusaway/1.2.1/onebusaway-1.2.1.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.onebusaway:onebusaway-application-modules:1.1.16: Could not find artifact org.onebusaway:onebusaway:pom:1.2.1 in public.onebusaway.org (http://nexus.onebusaway.org/content/groups/public/) and 'parent.relativePath' points at wrong local POM @ line 3, column 11
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project org.onebusaway:onebusaway-application-modules:1.1.16 (/home/ec2-user/onebusaway-application-modules/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.onebusaway:onebusaway-application-modules:1.1.16: Could not find artifact org.onebusaway:onebusaway:pom:1.2.1 in public.onebusaway.org (http://nexus.onebusaway.org/content/groups/public/) and 'parent.relativePath' points at wrong local POM @ line 3, column 11 -> [Help 2]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

Is there an alternate URL where I can grab one bus away dependencies?

Thanks

[sheldonabrown]

Sorry-- I've been having issues with the new server. I'll fix this weekend...

Sent from my mobile device (I'll be brief)

On Jun 23, 2017, at 7:41 PM, Ed Groth [email protected] wrote:

Hi everyone,

It looks like both http://developer.onebusaway.org/content/ and http://nexus.onebusaway.org/content/groups/public/ contain no depedancies.

The pom.xml from 1.1.16 which appears to be current stable branch references nexus: https://github.com/OneBusAway/onebusaway-application-modules/tree/onebusaway-application-modules-1.1.16

For me the build does not work:

Downloading: http://nexus.onebusaway.org/content/groups/public/org/onebusaway/onebusaway/1.2.1/onebusaway-1.2.1.pom [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM for org.onebusaway:onebusaway-application-modules:1.1.16: Could not find artifact org.onebusaway:onebusaway:pom:1.2.1 in public.onebusaway.org (http://nexus.onebusaway.org/content/groups/public/) and 'parent.relativePath' points at wrong local POM @ line 3, column 11 @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR]
[ERROR] The project org.onebusaway:onebusaway-application-modules:1.1.16 (/home/ec2-user/onebusaway-application-modules/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for org.onebusaway:onebusaway-application-modules:1.1.16: Could not find artifact org.onebusaway:onebusaway:pom:1.2.1 in public.onebusaway.org (http://nexus.onebusaway.org/content/groups/public/) and 'parent.relativePath' points at wrong local POM @ line 3, column 11 -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Is there an alternate URL where I can grab one bus away dependencies?

Thanks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[sheldonabrown]

Nexus is still available, but the URL has changed slightly:

http://nexus.onebusaway.org/nexus/content/groups/public/ Sent from my mobile device (I'll be brief)

On Jun 23, 2017, at 7:41 PM, Ed Groth [email protected] wrote:

Hi everyone,

It looks like both http://developer.onebusaway.org/content/ and http://nexus.onebusaway.org/content/groups/public/ contain no depedancies.

The pom.xml from 1.1.16 which appears to be current stable branch references nexus: https://github.com/OneBusAway/onebusaway-application-modules/tree/onebusaway-application-modules-1.1.16

For me the build does not work:

Downloading: http://nexus.onebusaway.org/content/groups/public/org/onebusaway/onebusaway/1.2.1/onebusaway-1.2.1.pom [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM for org.onebusaway:onebusaway-application-modules:1.1.16: Could not find artifact org.onebusaway:onebusaway:pom:1.2.1 in public.onebusaway.org (http://nexus.onebusaway.org/content/groups/public/) and 'parent.relativePath' points at wrong local POM @ line 3, column 11 @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR]
[ERROR] The project org.onebusaway:onebusaway-application-modules:1.1.16 (/home/ec2-user/onebusaway-application-modules/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for org.onebusaway:onebusaway-application-modules:1.1.16: Could not find artifact org.onebusaway:onebusaway:pom:1.2.1 in public.onebusaway.org (http://nexus.onebusaway.org/content/groups/public/) and 'parent.relativePath' points at wrong local POM @ line 3, column 11 -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Is there an alternate URL where I can grab one bus away dependencies?

Thanks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[ed-g]

@sheldonabrown thank you!!!

[sheldonabrown]

Ok -- I've been working on the configuration, and I've think I've got it back to where it should be.

If it isn't send me the links that break and I'll take a look.