JCenter from JFrog is shutting down?

[Taher Alkhateeb]

Hello Folks,

So I received an email and checked multiple websites [1] that JFrog's
service is coming to an end on May (this includes JCenter). I suppose we
should make the switch to maven central or whatever suitable repository
and hoping that all libraries exist over there as well.

It sucks to receive these news at such a short notice as they're
planning to kill the service on May 1st. I'm not sure if I'm late to the
party but I just received this news. Anyone heard of this and has plans
to switch out? How painful would you expect such a transition to be?

[1]

https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure/

- Taher

[Taher Alkhateeb]

Hi Everyone,

Upon further investigation it seems the only problematic library in the
repositories is org.ajoberstar:grgit which is responsible for commands
like gitPullAll, gitStatusAll and a few others. When I switched the core
components to mavenCentral nothing crashed thank goodness. It means at
least our libraries are not too exotic!

So it seems as a first step we need to convert all repositories from
jcenter() to mavenCentral() and then just figure out a way to get grgit
published to latest version on maven central or otherwise use a custom
URL for wherever the binary might be found.

I'm ready to help if needed and someone can guide me through. Do I just
create a PR in the repos?

- Taher

[David E Jones]

Thanks for bringing this up Taher. I tried switching and ended up having to add the Gradle plugins maven repo to a bunch of files for that and one other gradle plugin.

I just updated most of the components, not all yet. It does look like all will need to be updated, and all custom components people have that are built using Moqui that are using jcenter().

If I understood the timeline correctly they will stop receiving updates around the end of March, so that is effectively when the change needs to be completed but with a grace window through mid-year.

Interesting times... between this and ElasticSearch (which mind end up being a much bigger deal, but at least AWS is carrying the torch on open source ElasticSearch and Kibana for now). I wonder what else will fail in coming months? Whatever it is, we'll figure out something or other...

-David

--
You received this message because you are subscribed to the Google Groups "Moqui Ecosystem" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moqui+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/moqui/8bc81da0-1c76-7f5c-1ad2-ee3ddca0427d%40pythys.com.

[Taher Alkhateeb]

oops, sent to your personal email by offsight. Sorry

On 2/8/21 12:21 PM, Taher Alkhateeb wrote:

Hi David,

I saw the commit logs awesome thank you. Yeah we're getting stressed out with all these changes happening so fast when we have the majority of our projects deployed on top of moqui, with some of them holding critical systems. Maybe the safest bet for ES is to design the majority of our services to just use the entity facade and use ES only when needed for performance reasons.

To me all of what's happening is giving me a repeated lesson. Less is more. Less libraries, less entanglements, less external dependencies, less CDNs, less anything that might fail due to external uncontrolled factors.

- Taher

To view this discussion on the web visit https://groups.google.com/d/msgid/moqui/CAKBdU9fwtTPesF%3Dk-iuHe%2BR8uPSYFaDeBQ12FoWODCsduyZJBQ%40mail.gmail.com.