[jira] [Commented] (OFBIZ-12171) Handling the JCenter shutdown

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300245#comment-17300245 ]

Michael Brohl commented on OFBIZ-12171:
---------------------------------------

I also need to modify the file checksums accordingly for all branches.

> Handling the JCenter shutdown
> -----------------------------
>
>                 Key: OFBIZ-12171
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12171
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL APPLICATIONS, ALL COMPONENTS, ALL PLUGINS
>    Affects Versions: Release Branch 18.12, Trunk, 17.12.05
>            Reporter: Michael Brohl
>            Assignee: Michael Brohl
>            Priority: Major
>              Labels: backport-needed
>             Fix For: 18.12.01, Upcoming Branch, 17.12.06
>
>         Attachments: OFBIZ-12171-1712-README.patch
>
>
> Citing Taher's message at [2]:
> Hello Everyone,
>  
> I received emails and checked resources [1] that seem to confirm JCenter from JFrog is going down and that the last day of operation for the repository is going to be May 1st 2021.
>  
> This is a big deal as many running instances will crash unless updated, so not only do future versions of OFBiz need to adapt, but also existing installations.
>  
> I'm not sure how to best handle this? Especially for production instances out there on older versions of OFBiz. Maybe one solution is to host the existing libraries in some temporary location or try to migrate them to MavenCentral ... Whatever is the solution I think we should make a fast move.
>  
> [1] [https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter]
> [https://www.infoq.com/news/2021/02/jfrog-jcenter-bintray-closure]
> [2] [https://lists.apache.org/thread.html/rf8e883ca8b90d51ad9d6d48c46f8f1fcc1cb82cce802daeeab0b910a%40%3Cdev.ofbiz.apache.org%3E]
>  

--
This message was sent by Atlassian Jira
(v8.3.4#803005)