JFrog to shut down jcenter

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
30 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Michael Brohl-3
Thanks Nicolas and Jacques for your input.

I will try to update Gradle to the minimal version which fits and try to
proceed from ther.

Can someone please create a 17.12.06 release version in Jira? I
backported some of the latest bugfixes to the 17.12 release branch also
but was not able to set the fixed version because it is missing. I
assigned the release branch instead and would change that when we have
the version.

Thanks,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 16.02.21 um 09:17 schrieb Jacques Le Roux:

> Hi,
>
> I'd say that 17.12.06 is a bit apart. It's mostly because of JFrog
> shuting down jcenter that we decided to create a new releases after
> 17.12.05, even if a priori  that was not excluded.
>
> So I'm not against Nicolas's proposition...
>
> Jacques
>
> Le 15/02/2021 à 22:12, Michael Brohl a écrit :
>> Hi Nicolas,
>>
>> I thought that we are restricted to the Gradle version for 17.12,
>> aren‘t we?
>> If not I think it‘s easy to upgrade Gradle to just the first version
>> which supports metadataSources and proceed from there.
>>
>> Thanks,
>> Michael
>>
>>> Am 15.02.2021 um 19:08 schrieb Nicolas Malin
>>> <[hidden email]>:
>>>
>>> Hi Michel,
>>>
>>> Thanks for your works, I will check If I found a solution with Gradle
>>> 3.2.1. I keep in my  that a solution would be increase the Gradle
>>> version for the 17.12
>>>
>>> Nicolas
>>>
>>>> On 14/02/2021 16:51, Michael Brohl wrote:
>>>> For those who do not read the notifications for
>>>> https://issues.apache.org/jira/browse/OFBIZ-12171 I'd like to reach
>>>> you here too.
>>>>
>>>> I've already done the migration for trunk (committed) and r18.12
>>>> (PR's, to be committed in the next days).
>>>>
>>>> I've also started with the migration for 17.12, which will be tougher
>>>> because of the Gradle old version used there. There is no
>>>> metadataSources API to specify to pull a jar without a pom, which is
>>>> used for the flute dependency.
>>>>
>>>> Does someone know how to correct a pom in maven central? This is the
>>>> reason why metadataSources API was used for trunk and r18.12.
>>>>
>>>> Or does someone know a way to pull artefacts/jars from a repository
>>>> without a valid pom in Gradle 3.2.1?
>>>>
>>>> Any help is appreciated, thanks!
>>>>
>>>> Michael Brohl
>>>>
>>>> ecomify GmbH - www.ecomify.de
>>>>
>>>>
>>>>> Am 10.02.21 um 16:44 schrieb Michael Brohl:
>>>>> Ah, yes, thanks Jacques.
>>>>>
>>>>> See https://issues.apache.org/jira/browse/OFBIZ-12171 for the issue
>>>>> and links to the pull requests.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Michael
>>>>>
>>>>>
>>>>> Am 10.02.21 um 16:22 schrieb Jacques Le Roux:
>>>>>> Le 10/02/2021 à 11:06, Michael Brohl a écrit :
>>>>>>> I think I've got it solved for trunk, please see
>>>>>>> https://issues.apache.org/jira/browse/INFRA-21376 and the linked
>>>>>>> pull requests there.
>>>>>> I guess you mean OFBIZ-12171 rather no?
>>>>>>
>>>>>> Jacques
>>>>>>
Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Jacques Le Roux
Administrator
Done

Le 16/02/2021 à 10:33, Michael Brohl a écrit :
>
> Can someone please create a 17.12.06 release version in Jira?

Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Michael Brohl-3
Thanks, Jacques.

The migration for r17.12 is going to be tough.

If I update to the lowest Gradle version supporting metadataSources
(4.5.1) we need to change the build.gradle as well. There seem to be
incompatibilities with the clean* tasks.

I am also currently facing this bug:
https://www.jfrog.com/jira/browse/RTFACT-24621 causing compile errors
because UOUtils cannot be found.

I'm at it but it won't go as fast as I'd wish it would.

Regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 16.02.21 um 11:26 schrieb Jacques Le Roux:
> Done
>
> Le 16/02/2021 à 10:33, Michael Brohl a écrit :
>>
>> Can someone please create a 17.12.06 release version in Jira?
>
Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Nicolas Malin-2
Michael,

Do you have a patch or git branch to be sure that can reproduce the same
state from my part ?

Nicolas

On 16/02/2021 23:49, Michael Brohl wrote:

> Thanks, Jacques.
>
> The migration for r17.12 is going to be tough.
>
> If I update to the lowest Gradle version supporting metadataSources
> (4.5.1) we need to change the build.gradle as well. There seem to be
> incompatibilities with the clean* tasks.
>
> I am also currently facing this bug:
> https://www.jfrog.com/jira/browse/RTFACT-24621 causing compile errors
> because UOUtils cannot be found.
>
> I'm at it but it won't go as fast as I'd wish it would.
>
> Regards,
>
> Michael Brohl
>
> ecomify GmbH - www.ecomify.de
>
>
> Am 16.02.21 um 11:26 schrieb Jacques Le Roux:
>> Done
>>
>> Le 16/02/2021 à 10:33, Michael Brohl a écrit :
>>>
>>> Can someone please create a 17.12.06 release version in Jira?
>>
Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Michael Brohl-3
Hi Nicolas,

not yet. I'll provide a pull request with the latest changes soon.

Thanks,

Michael


Am 17.02.21 um 17:27 schrieb Nicolas Malin:

> Michael,
>
> Do you have a patch or git branch to be sure that can reproduce the same
> state from my part ?
>
> Nicolas
>
> On 16/02/2021 23:49, Michael Brohl wrote:
>> Thanks, Jacques.
>>
>> The migration for r17.12 is going to be tough.
>>
>> If I update to the lowest Gradle version supporting metadataSources
>> (4.5.1) we need to change the build.gradle as well. There seem to be
>> incompatibilities with the clean* tasks.
>>
>> I am also currently facing this bug:
>> https://www.jfrog.com/jira/browse/RTFACT-24621 causing compile errors
>> because UOUtils cannot be found.
>>
>> I'm at it but it won't go as fast as I'd wish it would.
>>
>> Regards,
>>
>> Michael Brohl
>>
>> ecomify GmbH - www.ecomify.de
>>
>>
>> Am 16.02.21 um 11:26 schrieb Jacques Le Roux:
>>> Done
>>>
>>> Le 16/02/2021 à 10:33, Michael Brohl a écrit :
>>>> Can someone please create a 17.12.06 release version in Jira?
Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Michael Brohl-3
I think I have a first solution for r17.12. The incompatibilities did
not occur again and the IOUtils problem could be solved by restricting
the commons-io dependency to a fixed version.

All tests pass on my machine.

Please test with your environments and let me know if you have any
remarks or ideas for optimization, thanks!

See pull requests

https://github.com/apache/ofbiz-plugins/pull/59
https://github.com/apache/ofbiz-framework/pull/278

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 18.02.21 um 17:53 schrieb Michael Brohl:

> Hi Nicolas,
>
> not yet. I'll provide a pull request with the latest changes soon.
>
> Thanks,
>
> Michael
>
>
> Am 17.02.21 um 17:27 schrieb Nicolas Malin:
>> Michael,
>>
>> Do you have a patch or git branch to be sure that can reproduce the same
>> state from my part ?
>>
>> Nicolas
>>
>> On 16/02/2021 23:49, Michael Brohl wrote:
>>> Thanks, Jacques.
>>>
>>> The migration for r17.12 is going to be tough.
>>>
>>> If I update to the lowest Gradle version supporting metadataSources
>>> (4.5.1) we need to change the build.gradle as well. There seem to be
>>> incompatibilities with the clean* tasks.
>>>
>>> I am also currently facing this bug:
>>> https://www.jfrog.com/jira/browse/RTFACT-24621 causing compile errors
>>> because UOUtils cannot be found.
>>>
>>> I'm at it but it won't go as fast as I'd wish it would.
>>>
>>> Regards,
>>>
>>> Michael Brohl
>>>
>>> ecomify GmbH - www.ecomify.de
>>>
>>>
>>> Am 16.02.21 um 11:26 schrieb Jacques Le Roux:
>>>> Done
>>>>
>>>> Le 16/02/2021 à 10:33, Michael Brohl a écrit :
>>>>> Can someone please create a 17.12.06 release version in Jira?
Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Jacques Le Roux
Administrator
+1, works for me

Jacques

Le 18/02/2021 à 22:18, Michael Brohl a écrit :

> I think I have a first solution for r17.12. The incompatibilities did not occur again and the IOUtils problem could be solved by restricting the
> commons-io dependency to a fixed version.
>
> All tests pass on my machine.
>
> Please test with your environments and let me know if you have any remarks or ideas for optimization, thanks!
>
> See pull requests
>
> https://github.com/apache/ofbiz-plugins/pull/59
> https://github.com/apache/ofbiz-framework/pull/278
>
> Michael Brohl
>
> ecomify GmbH - www.ecomify.de
>
>
> Am 18.02.21 um 17:53 schrieb Michael Brohl:
>> Hi Nicolas,
>>
>> not yet. I'll provide a pull request with the latest changes soon.
>>
>> Thanks,
>>
>> Michael
>>
>>
>> Am 17.02.21 um 17:27 schrieb Nicolas Malin:
>>> Michael,
>>>
>>> Do you have a patch or git branch to be sure that can reproduce the same
>>> state from my part ?
>>>
>>> Nicolas
>>>
>>> On 16/02/2021 23:49, Michael Brohl wrote:
>>>> Thanks, Jacques.
>>>>
>>>> The migration for r17.12 is going to be tough.
>>>>
>>>> If I update to the lowest Gradle version supporting metadataSources
>>>> (4.5.1) we need to change the build.gradle as well. There seem to be
>>>> incompatibilities with the clean* tasks.
>>>>
>>>> I am also currently facing this bug:
>>>> https://www.jfrog.com/jira/browse/RTFACT-24621 causing compile errors
>>>> because UOUtils cannot be found.
>>>>
>>>> I'm at it but it won't go as fast as I'd wish it would.
>>>>
>>>> Regards,
>>>>
>>>> Michael Brohl
>>>>
>>>> ecomify GmbH - www.ecomify.de
>>>>
>>>>
>>>> Am 16.02.21 um 11:26 schrieb Jacques Le Roux:
>>>>> Done
>>>>>
>>>>> Le 16/02/2021 à 10:33, Michael Brohl a écrit :
>>>>>> Can someone please create a 17.12.06 release version in Jira?

Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Michael Brohl-3
Hi everyone,

please help testing the jCenter to mavenCentral migration for trunk and
release branches r17.12/r18.12. See
https://issues.apache.org/jira/browse/OFBIZ-12171 and the linked pull
requests there.

Testing with different environments helps finding potential issues.

If there are no objections, I will merge the pull requests for all
branches coming weekend (after Friday, 26. February).

Thanks,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 19.02.21 um 10:42 schrieb Jacques Le Roux:

> +1, works for me
>
> Jacques
>
> Le 18/02/2021 à 22:18, Michael Brohl a écrit :
>> I think I have a first solution for r17.12. The incompatibilities did
>> not occur again and the IOUtils problem could be solved by
>> restricting the commons-io dependency to a fixed version.
>>
>> All tests pass on my machine.
>>
>> Please test with your environments and let me know if you have any
>> remarks or ideas for optimization, thanks!
>>
>> See pull requests
>>
>> https://github.com/apache/ofbiz-plugins/pull/59
>> https://github.com/apache/ofbiz-framework/pull/278
>>
>> Michael Brohl
>>
>> ecomify GmbH - www.ecomify.de
>>
>>
>> Am 18.02.21 um 17:53 schrieb Michael Brohl:
>>> Hi Nicolas,
>>>
>>> not yet. I'll provide a pull request with the latest changes soon.
>>>
>>> Thanks,
>>>
>>> Michael
>>>
>>>
>>> Am 17.02.21 um 17:27 schrieb Nicolas Malin:
>>>> Michael,
>>>>
>>>> Do you have a patch or git branch to be sure that can reproduce the
>>>> same
>>>> state from my part ?
>>>>
>>>> Nicolas
>>>>
>>>> On 16/02/2021 23:49, Michael Brohl wrote:
>>>>> Thanks, Jacques.
>>>>>
>>>>> The migration for r17.12 is going to be tough.
>>>>>
>>>>> If I update to the lowest Gradle version supporting metadataSources
>>>>> (4.5.1) we need to change the build.gradle as well. There seem to be
>>>>> incompatibilities with the clean* tasks.
>>>>>
>>>>> I am also currently facing this bug:
>>>>> https://www.jfrog.com/jira/browse/RTFACT-24621 causing compile errors
>>>>> because UOUtils cannot be found.
>>>>>
>>>>> I'm at it but it won't go as fast as I'd wish it would.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Michael Brohl
>>>>>
>>>>> ecomify GmbH - www.ecomify.de
>>>>>
>>>>>
>>>>> Am 16.02.21 um 11:26 schrieb Jacques Le Roux:
>>>>>> Done
>>>>>>
>>>>>> Le 16/02/2021 à 10:33, Michael Brohl a écrit :
>>>>>>> Can someone please create a 17.12.06 release version in Jira?
>
Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Michael Brohl-3
I have reopened https://issues.apache.org/jira/browse/OFBIZ-12171 for
necessary changes in the documentation (README.adoc) which references
JCenter.

Regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 22.02.21 um 17:47 schrieb Michael Brohl:

> Hi everyone,
>
> please help testing the jCenter to mavenCentral migration for trunk
> and release branches r17.12/r18.12. See
> https://issues.apache.org/jira/browse/OFBIZ-12171 and the linked pull
> requests there.
>
> Testing with different environments helps finding potential issues.
>
> If there are no objections, I will merge the pull requests for all
> branches coming weekend (after Friday, 26. February).
>
> Thanks,
>
> Michael Brohl
>
> ecomify GmbH - www.ecomify.de
>
>
> Am 19.02.21 um 10:42 schrieb Jacques Le Roux:
>> +1, works for me
>>
>> Jacques
>>
>> Le 18/02/2021 à 22:18, Michael Brohl a écrit :
>>> I think I have a first solution for r17.12. The incompatibilities
>>> did not occur again and the IOUtils problem could be solved by
>>> restricting the commons-io dependency to a fixed version.
>>>
>>> All tests pass on my machine.
>>>
>>> Please test with your environments and let me know if you have any
>>> remarks or ideas for optimization, thanks!
>>>
>>> See pull requests
>>>
>>> https://github.com/apache/ofbiz-plugins/pull/59
>>> https://github.com/apache/ofbiz-framework/pull/278
>>>
>>> Michael Brohl
>>>
>>> ecomify GmbH - www.ecomify.de
>>>
>>>
>>> Am 18.02.21 um 17:53 schrieb Michael Brohl:
>>>> Hi Nicolas,
>>>>
>>>> not yet. I'll provide a pull request with the latest changes soon.
>>>>
>>>> Thanks,
>>>>
>>>> Michael
>>>>
>>>>
>>>> Am 17.02.21 um 17:27 schrieb Nicolas Malin:
>>>>> Michael,
>>>>>
>>>>> Do you have a patch or git branch to be sure that can reproduce
>>>>> the same
>>>>> state from my part ?
>>>>>
>>>>> Nicolas
>>>>>
>>>>> On 16/02/2021 23:49, Michael Brohl wrote:
>>>>>> Thanks, Jacques.
>>>>>>
>>>>>> The migration for r17.12 is going to be tough.
>>>>>>
>>>>>> If I update to the lowest Gradle version supporting metadataSources
>>>>>> (4.5.1) we need to change the build.gradle as well. There seem to be
>>>>>> incompatibilities with the clean* tasks.
>>>>>>
>>>>>> I am also currently facing this bug:
>>>>>> https://www.jfrog.com/jira/browse/RTFACT-24621 causing compile
>>>>>> errors
>>>>>> because UOUtils cannot be found.
>>>>>>
>>>>>> I'm at it but it won't go as fast as I'd wish it would.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Michael Brohl
>>>>>>
>>>>>> ecomify GmbH - www.ecomify.de
>>>>>>
>>>>>>
>>>>>> Am 16.02.21 um 11:26 schrieb Jacques Le Roux:
>>>>>>> Done
>>>>>>>
>>>>>>> Le 16/02/2021 à 10:33, Michael Brohl a écrit :
>>>>>>>> Can someone please create a 17.12.06 release version in Jira?
>>
Reply | Threaded
Open this post in threaded view
|

Re: JFrog to shut down jcenter

Michael Brohl-3
It's weird but can someone please check and confirm:

With latest trunk and blocked jcenter.bintray.com (set to 127.0.0.1 in
/etc/hosts) OFBiz is not building anymore. There are several artefacts
which Gradle tries to load from JCenter again:

~/Projects/apache-ofbiz/ofbiz-framework ⑂trunk*  ./gradlew cleanAll build

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'ofbiz'.
 > Could not resolve all artifacts for configuration ':classpath'.
    > Could not resolve
se.patrikerdes:gradle-use-latest-versions-plugin:0.2.15.
      Required by:
          project : >
se.patrikerdes.use-latest-versions:se.patrikerdes.use-latest-versions.gradle.plugin:0.2.15
       > Could not resolve
se.patrikerdes:gradle-use-latest-versions-plugin:0.2.15.
          > Could not get resource
'https://plugins.gradle.org/m2/se/patrikerdes/gradle-use-latest-versions-plugin/0.2.15/gradle-use-latest-versions-plugin-0.2.15.module'.
             > Could not GET
'https://jcenter.bintray.com/se/patrikerdes/gradle-use-latest-versions-plugin/0.2.15/gradle-use-latest-versions-plugin-0.2.15.module'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connection refused (Connection
refused)
    > Could not resolve
com.github.jakemarsden:git-hooks-gradle-plugin:0.0.2.
      Required by:
          project : >
com.github.jakemarsden.git-hooks:com.github.jakemarsden.git-hooks.gradle.plugin:0.0.2
       > Could not resolve
com.github.jakemarsden:git-hooks-gradle-plugin:0.0.2.
          > Could not get resource
'https://plugins.gradle.org/m2/com/github/jakemarsden/git-hooks-gradle-plugin/0.0.2/git-hooks-gradle-plugin-0.0.2.module'.
             > Could not GET
'https://jcenter.bintray.com/com/github/jakemarsden/git-hooks-gradle-plugin/0.0.2/git-hooks-gradle-plugin-0.0.2.module'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connection refused (Connection
refused)
    > Could not resolve org.codehaus.groovy:groovy-all:2.4.7.
      Required by:
          project : >
at.bxm.svntools:at.bxm.svntools.gradle.plugin:2.2.1 >
at.bxm.gradleplugins:gradle-svntools-plugin:2.2.1
       > Could not resolve org.codehaus.groovy:groovy-all:2.4.7.
          > Could not get resource
'https://plugins.gradle.org/m2/org/codehaus/groovy/groovy-all/2.4.7/groovy-all-2.4.7.pom'.
             > Could not GET
'https://jcenter.bintray.com/org/codehaus/groovy/groovy-all/2.4.7/groovy-all-2.4.7.pom'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connection refused (Connection
refused)
    > Could not resolve org.tmatesoft.svnkit:svnkit:1.8.12.
      Required by:
          project : >
at.bxm.svntools:at.bxm.svntools.gradle.plugin:2.2.1 >
at.bxm.gradleplugins:gradle-svntools-plugin:2.2.1
       > Could not resolve org.tmatesoft.svnkit:svnkit:1.8.12.
          > Could not get resource
'https://plugins.gradle.org/m2/org/tmatesoft/svnkit/svnkit/1.8.12/svnkit-1.8.12.pom'.
             > Could not GET
'https://jcenter.bintray.com/org/tmatesoft/svnkit/svnkit/1.8.12/svnkit-1.8.12.pom'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connection refused (Connection
refused)
    > Could not resolve org.ysb33r.gradle:grolifant:0.12.1.
      Required by:
          project : >
org.asciidoctor.convert:org.asciidoctor.convert.gradle.plugin:2.4.0 >
org.asciidoctor:asciidoctor-gradle-jvm:2.4.0
          project : >
org.asciidoctor.convert:org.asciidoctor.convert.gradle.plugin:2.4.0 >
org.asciidoctor:asciidoctor-gradle-jvm:2.4.0 >
org.asciidoctor:asciidoctor-gradle-base:2.4.0
       > Could not resolve org.ysb33r.gradle:grolifant:0.12.1.
          > Could not get resource
'https://plugins.gradle.org/m2/org/ysb33r/gradle/grolifant/0.12.1/grolifant-0.12.1.pom'.
             > Could not GET
'https://jcenter.bintray.com/org/ysb33r/gradle/grolifant/0.12.1/grolifant-0.12.1.pom'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connection refused (Connection
refused)
    > Could not resolve org.owasp:dependency-check-core:6.0.3.
      Required by:
          project : >
org.owasp.dependencycheck:org.owasp.dependencycheck.gradle.plugin:6.0.3
 > org.owasp:dependency-check-gradle:6.0.3
       > Could not resolve org.owasp:dependency-check-core:6.0.3.
          > Could not get resource
'https://plugins.gradle.org/m2/org/owasp/dependency-check-core/6.0.3/dependency-check-core-6.0.3.pom'.
             > Could not GET
'https://jcenter.bintray.com/org/owasp/dependency-check-core/6.0.3/dependency-check-core-6.0.3.pom'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connection refused (Connection
refused)
    > Could not resolve org.owasp:dependency-check-utils:6.0.3.
      Required by:
          project : >
org.owasp.dependencycheck:org.owasp.dependencycheck.gradle.plugin:6.0.3
 > org.owasp:dependency-check-gradle:6.0.3
       > Could not resolve org.owasp:dependency-check-utils:6.0.3.
          > Could not get resource
'https://plugins.gradle.org/m2/org/owasp/dependency-check-utils/6.0.3/dependency-check-utils-6.0.3.pom'.
             > Could not GET
'https://jcenter.bintray.com/org/owasp/dependency-check-utils/6.0.3/dependency-check-utils-6.0.3.pom'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connection refused (Connection
refused)
    > Could not resolve net.gpedro.integrations.slack:slack-webhook:1.4.0.
      Required by:
          project : >
org.owasp.dependencycheck:org.owasp.dependencycheck.gradle.plugin:6.0.3
 > org.owasp:dependency-check-gradle:6.0.3
       > Could not resolve
net.gpedro.integrations.slack:slack-webhook:1.4.0.
          > Could not get resource
'https://plugins.gradle.org/m2/net/gpedro/integrations/slack/slack-webhook/1.4.0/slack-webhook-1.4.0.pom'.
             > Could not GET
'https://jcenter.bintray.com/net/gpedro/integrations/slack/slack-webhook/1.4.0/slack-webhook-1.4.0.pom'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connection refused (Connection
refused)
    > Could not resolve com.thoughtworks.xstream:xstream:1.4.10.
      Required by:
          project : >
com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin:0.36.0
 > com.github.ben-manes:gradle-versions-plugin:0.36.0
       > Could not resolve com.thoughtworks.xstream:xstream:1.4.10.
          > Could not get resource
'https://plugins.gradle.org/m2/com/thoughtworks/xstream/xstream/1.4.10/xstream-1.4.10.pom'.
             > Could not GET
'https://jcenter.bintray.com/com/thoughtworks/xstream/xstream/1.4.10/xstream-1.4.10.pom'.
                > Connect to jcenter.bintray.com:443
[jcenter.bintray.com/127.0.0.1] failed: Connection refused (Connection
refused)

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 23s


Please check, I want to exclude a problem on my side.

Thanks,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 10.03.21 um 12:44 schrieb Michael Brohl:

> I have reopened https://issues.apache.org/jira/browse/OFBIZ-12171 for
> necessary changes in the documentation (README.adoc) which references
> JCenter.
>
> Regards,
>
> Michael Brohl
>
> ecomify GmbH - www.ecomify.de
>
>
> Am 22.02.21 um 17:47 schrieb Michael Brohl:
>> Hi everyone,
>>
>> please help testing the jCenter to mavenCentral migration for trunk
>> and release branches r17.12/r18.12. See
>> https://issues.apache.org/jira/browse/OFBIZ-12171 and the linked pull
>> requests there.
>>
>> Testing with different environments helps finding potential issues.
>>
>> If there are no objections, I will merge the pull requests for all
>> branches coming weekend (after Friday, 26. February).
>>
>> Thanks,
>>
>> Michael Brohl
>>
>> ecomify GmbH - www.ecomify.de
>>
>>
>> Am 19.02.21 um 10:42 schrieb Jacques Le Roux:
>>> +1, works for me
>>>
>>> Jacques
>>>
>>> Le 18/02/2021 à 22:18, Michael Brohl a écrit :
>>>> I think I have a first solution for r17.12. The incompatibilities
>>>> did not occur again and the IOUtils problem could be solved by
>>>> restricting the commons-io dependency to a fixed version.
>>>>
>>>> All tests pass on my machine.
>>>>
>>>> Please test with your environments and let me know if you have any
>>>> remarks or ideas for optimization, thanks!
>>>>
>>>> See pull requests
>>>>
>>>> https://github.com/apache/ofbiz-plugins/pull/59
>>>> https://github.com/apache/ofbiz-framework/pull/278
>>>>
>>>> Michael Brohl
>>>>
>>>> ecomify GmbH - www.ecomify.de
>>>>
>>>>
>>>> Am 18.02.21 um 17:53 schrieb Michael Brohl:
>>>>> Hi Nicolas,
>>>>>
>>>>> not yet. I'll provide a pull request with the latest changes soon.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Michael
>>>>>
>>>>>
>>>>> Am 17.02.21 um 17:27 schrieb Nicolas Malin:
>>>>>> Michael,
>>>>>>
>>>>>> Do you have a patch or git branch to be sure that can reproduce
>>>>>> the same
>>>>>> state from my part ?
>>>>>>
>>>>>> Nicolas
>>>>>>
>>>>>> On 16/02/2021 23:49, Michael Brohl wrote:
>>>>>>> Thanks, Jacques.
>>>>>>>
>>>>>>> The migration for r17.12 is going to be tough.
>>>>>>>
>>>>>>> If I update to the lowest Gradle version supporting metadataSources
>>>>>>> (4.5.1) we need to change the build.gradle as well. There seem
>>>>>>> to be
>>>>>>> incompatibilities with the clean* tasks.
>>>>>>>
>>>>>>> I am also currently facing this bug:
>>>>>>> https://www.jfrog.com/jira/browse/RTFACT-24621 causing compile
>>>>>>> errors
>>>>>>> because UOUtils cannot be found.
>>>>>>>
>>>>>>> I'm at it but it won't go as fast as I'd wish it would.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Michael Brohl
>>>>>>>
>>>>>>> ecomify GmbH - www.ecomify.de
>>>>>>>
>>>>>>>
>>>>>>> Am 16.02.21 um 11:26 schrieb Jacques Le Roux:
>>>>>>>> Done
>>>>>>>>
>>>>>>>> Le 16/02/2021 à 10:33, Michael Brohl a écrit :
>>>>>>>>> Can someone please create a 17.12.06 release version in Jira?
>>>
12