Incident: Maven dependencies are failing with a 501 error

hbz / lobid

Linking Open Bibliographic Data

https://lobid.org/

Eclipse Public License 2.0

15 stars 4 forks source link

Incident: Maven dependencies are failing with a 501 error #415

Closed dr0i closed 4 years ago

dr0i commented 4 years ago

Maven central repo switched to https. Since 2020-03-13 (at least lobid-resources) dependencies didn't resolve. This can be fixed by using the newest maven or by adding .m2/settings.xml with defining a https url to maven2 central. Did the latter.

So this fixes everything done at weywot1. Are there other server or buidling systems (gradle) which may be affected @fsteeg ?

dr0i commented 4 years ago

Note: Affected are only those repos which have been added or updated a library recently. This was true for lobid-resources due to an jackson security fix merged at 2020-03-12.

I see production of lobid-resources was not affected because it wasn't updated due to a merge conflict. So production was 15 commits behind. Opened a new issue dealing with this.

dr0i commented 4 years ago

Added ~/.m2/settings.xml at quaoar1 for what it's worth.

dr0i commented 4 years ago

Triggered building of wikidata-geo-nwbib-index and consecutively full indexing of staging.

dr0i commented 4 years ago

We decided offline to no more github-click-merging some security library updates. We shall do this at command line and check if build is OK. Checked crontab and am quite sure that other apps are not concerned or are good with the updates of settings.xml. Closing this issue.