Okapi maven repository stop working

[Former user]

Hi. We are using Okapi framework and today the CI/CD job failed when tries to fetch the Okapi lib from maven repository, release and snapshot are not available.

http://repository-okapi.forge.cloudbees.com/release/net/sf/okapi/okapi-core/0.35/okapi-core-0.35.jar

is there any new changes on the repository or did it move to some other place.

Thanks

[YvesS]

Yes, CloudBees has stopped its Jenkins operations this week-end.

now, the 0.36 release of Okapi is available on Maven Central: https://search.maven.org/search?q=net.sf.okapi The snapshots are available on https://oss.sonatype.org/content/repositories/snapshots/ but that starts at 0.37-SNAPSHOT only.

I guess we didn't expect the repositories to be discarded, just the build to be discontinued. We'll have to re-deploy 0.35.

[Gabriele De Carli]

Hi guys, any news on the deploy on central of the previous version of okapi ?

also

<artifactId>okapi-lib-tkit</artifactId> <groupId>net.sf.okapi.lib</groupId> <version>36</version>

don't exist on maven central, what happen? is it decommissioned? is it published with another artifact-id? didn't find anything in the changelogs

[YvesS]

Indeed, it looks like we completely forgot to include that change in the change log. That change was done over many weeks between m35 and m36 and we somehow managed to miss including it in the change log. That library was used with the JSON skeleton which was not working anymore since a while and was not not maintained any more. The few parts still in use have been moved to other package. I'll try to get more info on this.

As for m35: yes, it's not in Maven central and the previous repositories have been removed by CloudBees. Re-publishing m35 in Maven is quite complicated and we have no plan to do that so far. Some of today's conference call (https://groups.google.com/forum/#!topic/okapi-devel/jaYebv-aqEU) was about this, and we are still thinking about how to provide m35.

[Gabriele De Carli]

Thanks for the info, I've to find a workaround on this our build process is heavily effected by the removal of the old repository, correct me if I'm wrong but for what I'm understanding the 0.35 libs will not be put back online, is it correct?

[Gabriele De Carli]

any news on the republishing of the 0.35?

[YvesS]

No progress so far. We were a bit blindsided by the fact CloudBees dropped also support for the existing repositories.

One solution is to rebuild the m35 code on your machine. The branch is here: https://bitbucket.org/okapiframework/okapi/commits/tag/m35 But that's not really a good solution making 0.35 available to all, or even an internal group of developers.

There maybe a way to have at least a "poor man" repository on GitHub: https://stackoverflow.com/questions/14013644/hosting-a-maven-repository-on-github We'll have to look at this.

[YvesS]

Mihai, worked some magic and managed to publish 0.35 on Maven Central. So you should be able to just remove the <repository> entry referring to CloudBees from your POM file and things should go back to normal.

Ideally you probably want to try to move to 0.36 as 0.35 is the last version with Java 7 support.

[Gabriele De Carli]

Kudos to Mihai, yes we are moving to 0.36 but having the 0.35 will allow us to run our build pipeline to publish hot fixes while doing the upgrade.

Thx for the support and happy new year btw.