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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[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=17299402#comment-17299402 ]

Jacques Le Roux commented on OFBIZ-12171:
-----------------------------------------

Hi Michael,

I can't reproduce locally:

C:\projectsASF\Git\ofbiz-framework>type C:\Windows\System32\drivers\etc\hosts

{noformat}
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#       127.0.0.1       localhost
#       ::1             localhost

127.0.0.1       localhost
127.0.0.1 jcenter.bintray.com
{noformat}

{noformat}
C:\projectsASF\Git\ofbiz-framework>g clean build

C:\projectsASF\Git\ofbiz-framework>gradlew --no-daemon clean build
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/6.5.1/userguide/gradle_daemon.html.
Daemon will be stopped at the end of the build stopping after processing

> Configure project :
You are using one or more deprecated Asciidoctor Gradle plugin features. To help with migration run with --warning-mode=all.

> Task :clean

> Task :compileJava
Z:\Gradle\caches\modules-2\files-2.1\org.apache.tomcat\tomcat-el-api\9.0.43\ce73ae606e6bee7df54e4a7701e51886e793d3ac\tomcat-el-api-9.0.43.jar(javax/el/ExpressionFactory.class): warning: Cannot find annotation method 'value()' in type 'Se
rviceConsumer': class file for aQute.bnd.annotation.spi.ServiceConsumer not found
1 warning

> Task :compileGroovy
> Task :processResources
> Task :classes
> Task :jar
> Task :startScripts
> Task :distTar
> Task :distZip
> Task :assemble
> Task :compileGroovyScriptsJava NO-SOURCE
> Task :compileGroovyScriptsGroovy SKIPPED
> Task :processGroovyScriptsResources NO-SOURCE
> Task :groovyScriptsClasses UP-TO-DATE
> Task :checkstyleGroovyScripts NO-SOURCE

> Task :checkstyleMain
Checkstyle rule violations were found. See the report at: file:///C:/projectsASF/Git/ofbiz-framework/build/reports/checkstyle/main.html
Checkstyle files with violations: 63
Checkstyle violations by severity: [error:127]


> Task :compileTestJava
> Task :compileTestGroovy
> Task :processTestResources
> Task :testClasses
> Task :checkstyleTest
> Task :test
> Task :check
> Task :build

BUILD SUCCESSFUL in 4m 38s
14 actionable tasks: 14 executed
C:\projectsASF\Git\ofbiz-framework>git branch
  release17.12
  release18.12
* trunk

C:\projectsASF\Git\ofbiz-framework>
{noformat}

> 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)