Hi Nicolas,

I have checked the jcenter problems together with Wiebke and Benjamin during the week.

The both were not able to get to the build failure with deactivated access to jcenter, even with removing the Gradle caches, wrappers and new initialisation with init-gradle-wrapper.

I just did another check, also removing everything and it is now also working without problems and a successful build. It might have been some mixture with the Gradle caches and different OFBiz versions/dependencies which lead to the previous error.

So with 3 people on the ecomify side, we cannot reproduce the problem and I would say it is solved. It's just a bit confusing that now you have at least one remaining problem.

But given the Gradle statement you mentioned, we should be good to go.

Thanks for checking and best regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 15.10.21 um 14:51 schrieb Nicolas Malin:
Hello Michael,

Gradle community create a dedicate page for this problem [1], If my
understanding is correct, we (massively you :) ) already done the job to
prepare the shutdown, and for the current potential issue that we have,
I read :

  > Impact to Gradle plugins
  >   Behind the scenes, the Gradle Plugin Portal
<https://plugins.gradle.org/> uses JCenter to resolve dependencies of
plugins. We will be migrating the Plugin Portal away from JCenter before
the final shutdown. Builds will not need to make changes while the
Plugin Portal migrates away from JCenter.
  > Resolving existing plugins
  >   Existing plugins will continue to resolve in the same way they do
today. No changes should need to be made to your builds.

Currently we have

        > Could not resolve com.thoughtworks.xstream:xstream:1.4.17.
          > Could not get resource
'https://plugins.gradle.org/m2/com/thoughtworks/xstream/xstream/1.4.17/xstream-1.4.17.pom'.
             > Could not GET
'https://jcenter.bintray.com/com/thoughtworks/xstream/xstream/1.4.17/xstream-1.4.17.pom'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connexion refusée (Connection
refused)

The build call https://plugins.gradle.org/m2 so finally no problem for
us if we believe on gradle community.

Do you confirm my analyze ?

Nicolas

[1] https://blog.gradle.org/jcenter-shutdown

On 12/10/2021 10:24, Michael Brohl wrote:
Hi Nicolas, all,

I just checked the jcenter problem [1] and it still remains when you
deactivate access to jcenter.bintray.com as shown in [2] and clean the
gradle cache.

According to [1], we'll have to upgrade Gradle itself for the branch.

Best regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


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

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



Am 07.10.21 um 18:20 schrieb Michael Brohl:
Hi Nicolas,

thanks for your message! I really would like to work on it but I am
currently (over)occupied with client projects.

I'll try to organise some support with the ecomify team. I am also
interested in getting the 18.12 release out as we have some projects
based on it.

Thanks and regards,

Michael


Am 07.10.21 um 18:04 schrieb Nicolas Malin:
Hello Michael,

Any chance to work together on it soon ?

Nicolas

On 29/09/2021 09:20, Nicolas Malin wrote:
Hello Michael,

No problem to resolve these issue before.

Currently for jcenter, I tried to restart from scratch and from my
part
I didn't see any issue but sure I missed something

Concerning the DiskFileItem, I tried to work on it, but without
success
to spot the problem.

If you have some time to work on it together by VC it would be a
pleasure !

Nicolas

On 28/09/2021 18:29, Michael Brohl wrote:
Hi Nicolas,

there a issues which I think should be fixed before an 18.12 release,
for example the JCenter migration problem [1] or the DiskFileItem
topic [2].

There are many more bugs also which I didn't check.

Regards,

Michael


[1] https://issues.apache.org/jira/browse/OFBIZ-12171

[2] https://issues.apache.org/jira/browse/OFBIZ-12016

Reply via email to