Is the publishMavenPublicationToOSSRHRepository task rebuilding the engine?
Also, i’ve been moving my stuff to github package registry, it is not too bad after all, the authentication setup is an one time thing and it is also possible to use it “anonymously” with this plugin GitHub - 0ffz/gpr-for-gradle: Gradle plugin for adding maven repos on Github Packages in one line.
Would you agree to deploy there too? We don’t need to change the buildscript since I can do it from the actions workflow with curl.
Last week, JFrog changed its mind and announced that they will keep JCenter available as a read-only archive for Maven artifacts. However, I’m finding many broken links.
Now that makes me trust them even less. I guess they are trying to mitigate losses, I know several large commercial clients using their paid services who are migrating to other solutions because they no longer trust bintray as part of their long term strategy. But really at this point they just need to decide on a path and stick to it, them changing their mind every 6 months is the last thing anyone wants.
Yeah, I used this sort of circular reasoning to wonder if they were actually circling the drain.
I can understand them being cash poor or something but they had to know that cutting off the service would look really bad… so they had to be really cash-poor to do it… which then looks even worse. And they had to know that other software companies that they do business with would also think this.
…so how desperate to cut losses were they that even given all of that they chose to sunset it. Not good.
Or the alternative, some executive manager was looking to pad his bonus this year and would not be deterred by any sane person underneath him. And now they are reaping the consequences. Which I’m not sure is any better.
Honestly, the fact that they didn’t even reach out to the gradle orgs, etc. to see about some kind of transition or potentially taking over the domain and base hosting (gradle templates include jcenter by default)… makes me think the second option is the more likely.
Cash hungry and looking to divest services without losing face looks a little different than one they’ve done. I guess time will tell.
At any rate, I’m glad my versions are still available indefinitely now while I learn all of the different hoops for maven central.
Gradle started to whine about the jCenter. For me it is only the com.simsilica that I depend on jCenter. Obviously this will work just fine for what I recon is maybe a fairly long time. But just thought to inquire the current status of com.simsilica Maven status?
When I have like 4-5 days free to do nothing but f*ck with gradle scripts then I will do it.
Until then, we can all flip bintray the bird and vow never to do business with them.
Eventually it will come to a head when I need to push updates but until then I’m trying to make progress on my game so that I don’t have to close my business, etc…