[
https://issues.apache.org/jira/browse/OFBIZ-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280155#comment-17280155
]
Michael Brohl commented on OFBIZ-12171:
---------------------------------------
Using maven central with configured url to https://repo1.maven.org/maven2 the
number of errors is drastically reduced to about 7 problems:
{noformat}
> Could not resolve all files for configuration ':runtimeClasspath'.
> Could not find
com.sun.syndication:com.springsource.com.sun.syndication:1.0.0.
Searched in the following locations:
-
https://repo1.maven.org/maven2/com/sun/syndication/com.springsource.com.sun.syndication/1.0.0/com.springsource.com.sun.syndication-1.0.0.pom
If the artifact you are trying to retrieve can be found in the repository
but without metadata in 'Maven POM' format, you need to adjust the
'metadataSources { ... }' of the repository declaration.
Required by:
project :
> Could not find net.fortuna.ical4j:ical4j:1.0-rc3-atlassian-11.
Searched in the following locations:
-
https://repo1.maven.org/maven2/net/fortuna/ical4j/ical4j/1.0-rc3-atlassian-11/ical4j-1.0-rc3-atlassian-11.pom
If the artifact you are trying to retrieve can be found in the repository
but without metadata in 'Maven POM' format, you need to adjust the
'metadataSources { ... }' of the repository declaration.
Required by:
project :
> Could not find org.opensaml:opensaml:1.1b.
Searched in the following locations:
-
https://repo1.maven.org/maven2/org/opensaml/opensaml/1.1b/opensaml-1.1b.pom
If the artifact you are trying to retrieve can be found in the repository
but without metadata in 'Maven POM' format, you need to adjust the
'metadataSources { ... }' of the repository declaration.
Required by:
project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5
> Could not find org.inspektr:inspektr-core:0.7.0.
Searched in the following locations:
-
https://repo1.maven.org/maven2/org/inspektr/inspektr-core/0.7.0/inspektr-core-0.7.0.pom
If the artifact you are trying to retrieve can be found in the repository
but without metadata in 'Maven POM' format, you need to adjust the
'metadataSources { ... }' of the repository declaration.
Required by:
project : > project :plugins:ldap > org.jasig.cas:cas-server-core:3.3.5
> Could not find org.restlet.jee:org.restlet:2.4.0.
Searched in the following locations:
-
https://repo1.maven.org/maven2/org/restlet/jee/org.restlet/2.4.0/org.restlet-2.4.0.pom
If the artifact you are trying to retrieve can be found in the repository
but without metadata in 'Maven POM' format, you need to adjust the
'metadataSources { ... }' of the repository declaration.
Required by:
project : > project :plugins:solr > org.apache.solr:solr-core:8.5.2
> Could not find org.restlet.jee:org.restlet.ext.servlet:2.4.0.
Searched in the following locations:
-
https://repo1.maven.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2.4.0/org.restlet.ext.servlet-2.4.0.pom
If the artifact you are trying to retrieve can be found in the repository
but without metadata in 'Maven POM' format, you need to adjust the
'metadataSources { ... }' of the repository declaration.
Required by:
project : > project :plugins:solr > org.apache.solr:solr-core:8.5.2
> Could not resolve org.milyn:flute:1.3.
Required by:
project : > project :plugins:birt >
org.eclipse.birt.runtime:viewservlets:4.5.0 >
org.eclipse.birt.runtime:org.eclipse.birt.runtime:4.4.1
> Could not resolve org.milyn:flute:1.3.
> inconsistent module metadata found. Descriptor: milyn:flute:1.3
Errors: bad group: expected='org.milyn' found='milyn'{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
> Priority: Major
>
> 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)
