JFrog to shut down jcenter

[Taher Alkhateeb-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

[Michael Brohl-3]

Hi Taher,

thanks for bringing this up!

This is indeed something we should care about quite soon. It will affect
the upcoming 18.12 release as well as supporting the 17.12 release for
which we might have to do another release handling this.

I created a Jira issue for it at [1].

I also did a first check with wiped Gradle cache and removed JCenter
reference and put the results in the Jira as well. There are about 78
libraries which are not found at Maven central.

While there are a lot of Apache libraries which we can assume to be
moved to Maven central soon, there are also some libraries which might
not be maintained actively.

Will think about how to handle this and come back here.

Thanks,

Michael Brohl

ecomify GmbH - www.ecomify.de


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

PS: great to hear from you again, it's been a while, Taher.


Am 05.02.21 um 22:04 schrieb Taher Alkhateeb:

> 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

[Jacques Le Roux]

Hi Taher,

Yes, yesterday I moderated/accepted, I guess the same message you received, to the private ML. We received it in the private ML because we (PMC
members) have a credential we use to upload Gradle wrappers version on Bintray:
https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray
So it's also a release concern...

I agree we should not procrastinate... Fortunately we have 2 months to decide and act...

We should try to use MavenCentral as much as possible, but IIRW maybe it will not be enough.

HTH

Jacques

Le 05/02/2021 à 22:04, Taher Alkhateeb a écrit :

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

[Michael Brohl-3]

Infra is also at it, see https://issues.apache.org/jira/browse/INFRA-21376

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 06.02.21 um 11:29 schrieb Michael Brohl:

> Hi Taher,
>
> thanks for bringing this up!
>
> This is indeed something we should care about quite soon. It will
> affect the upcoming 18.12 release as well as supporting the 17.12
> release for which we might have to do another release handling this.
>
> I created a Jira issue for it at [1].
>
> I also did a first check with wiped Gradle cache and removed JCenter
> reference and put the results in the Jira as well. There are about 78
> libraries which are not found at Maven central.
>
> While there are a lot of Apache libraries which we can assume to be
> moved to Maven central soon, there are also some libraries which might
> not be maintained actively.
>
> Will think about how to handle this and come back here.
>
> Thanks,
>
> Michael Brohl
>
> ecomify GmbH - www.ecomify.de
>
>
> [1] https://issues.apache.org/jira/browse/OFBIZ-12171
>
> PS: great to hear from you again, it's been a while, Taher.
>
>
> Am 05.02.21 um 22:04 schrieb Taher Alkhateeb:
>> 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

[Taher Alkhateeb-2]

Hi Folks.

I need to stress something very important here. The problem is not at
all future versions, the big problem is existing versions.

If you have a production system running and JFrog pulls the plug on May
1st, you cannot run the server unless you have some existing gradle
cache and you need to pass the offline flag to ignore the jcenter
repository.

So any solution here is a painful one. Here are the solutions I can
think of:

- create a mirror of jcenter that at least covers the requirements of
older OFBiz versions. The problem here is that people who worked on
older versions of trunk are going to hit a wall. It's also hard and
costly to setup a mirrored repo.
- create a compressed archive of all cache artifacts for each major version.
- Inform users to make a backup copy of gradle cache archives if they
are on an older version and encourage them to upgrade ASAP.
- create a patch file for each major release that alters dependencies to
switch to mavenCentral. The patch would mostly affect build.gradle.
- Make commits directly to all release branches. However the problem
here is that some people are running on old releases and cannot upgrade
immediately due to merge conflicts and whatnot.

This is a very nasty move by JFrog, they hurt a lot of projects. Android
depends on JCenter, React Native, OFBiz, and numerous other projects and
libraries that go even beyond the java eco-system.

- Taher

On 2/6/21 1:30 PM, Jacques Le Roux wrote:

> Hi Taher,
>
> Yes, yesterday I moderated/accepted, I guess the same message you
> received, to the private ML. We received it in the private ML because
> we (PMC members) have a credential we use to upload Gradle wrappers
> version on Bintray:
> https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray 
>
> So it's also a release concern...
>
> I agree we should not procrastinate... Fortunately we have 2 months to
> decide and act...
>
> We should try to use MavenCentral as much as possible, but IIRW maybe
> it will not be enough.
>
> HTH
>
> Jacques
>
> Le 05/02/2021 à 22:04, Taher Alkhateeb a écrit :
>> 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
>>

[Michael Brohl-3]

Hi Taher,

absolutely, this is a major problem for production projects and for them
the timeframe is very short.

Thinking about your list of possible actions, the most convenient
(simplest) way for all parties would be to provide patches for the
affected release versions IF we are able to solve this just with
repository configuration.

Users can apply those patches or adjust their installations guided by us.

We might need to provide alternative download options for artifacts
which are not hosted by maven central, google or other central
repositories. Hopefully, those are only a few. I am currently checking
this. For trunk, we are at about seven libraries missing when using
maven central.

Of course, we should have a good communication towards our users
providing information and solutions through our various social media
channels, blog etc.

Let's gather some more information and make a plan when we have more
insight of the real impact (technically).

Best regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 06.02.21 um 12:01 schrieb Taher Alkhateeb:

> Hi Folks.
>
> I need to stress something very important here. The problem is not at
> all future versions, the big problem is existing versions.
>
> If you have a production system running and JFrog pulls the plug on
> May 1st, you cannot run the server unless you have some existing
> gradle cache and you need to pass the offline flag to ignore the
> jcenter repository.
>
> So any solution here is a painful one. Here are the solutions I can
> think of:
>
> - create a mirror of jcenter that at least covers the requirements of
> older OFBiz versions. The problem here is that people who worked on
> older versions of trunk are going to hit a wall. It's also hard and
> costly to setup a mirrored repo.
> - create a compressed archive of all cache artifacts for each major
> version.
> - Inform users to make a backup copy of gradle cache archives if they
> are on an older version and encourage them to upgrade ASAP.
> - create a patch file for each major release that alters dependencies
> to switch to mavenCentral. The patch would mostly affect build.gradle.
> - Make commits directly to all release branches. However the problem
> here is that some people are running on old releases and cannot
> upgrade immediately due to merge conflicts and whatnot.
>
> This is a very nasty move by JFrog, they hurt a lot of projects.
> Android depends on JCenter, React Native, OFBiz, and numerous other
> projects and libraries that go even beyond the java eco-system.
>
> - Taher
>
> On 2/6/21 1:30 PM, Jacques Le Roux wrote:
>> Hi Taher,
>>
>> Yes, yesterday I moderated/accepted, I guess the same message you
>> received, to the private ML. We received it in the private ML because
>> we (PMC members) have a credential we use to upload Gradle wrappers
>> version on Bintray:
>> https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray 
>>
>> So it's also a release concern...
>>
>> I agree we should not procrastinate... Fortunately we have 2 months
>> to decide and act...
>>
>> We should try to use MavenCentral as much as possible, but IIRW maybe
>> it will not be enough.
>>
>> HTH
>>
>> Jacques
>>
>> Le 05/02/2021 à 22:04, Taher Alkhateeb a écrit :
>>> 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
>>>

[Jacques Le Roux]

That's a good news, thanks Michael

Let's follow what we can expect from Infra, those guys often do marvel...

Jacques

Le 06/02/2021 à 11:42, Michael Brohl a écrit :

> Infra is also at it, see https://issues.apache.org/jira/browse/INFRA-21376
>
> Michael Brohl
>
> ecomify GmbH - www.ecomify.de
>
>
> Am 06.02.21 um 11:29 schrieb Michael Brohl:
>> Hi Taher,
>>
>> thanks for bringing this up!
>>
>> This is indeed something we should care about quite soon. It will affect the upcoming 18.12 release as well as supporting the 17.12 release for
>> which we might have to do another release handling this.
>>
>> I created a Jira issue for it at [1].
>>
>> I also did a first check with wiped Gradle cache and removed JCenter reference and put the results in the Jira as well. There are about 78
>> libraries which are not found at Maven central.
>>
>> While there are a lot of Apache libraries which we can assume to be moved to Maven central soon, there are also some libraries which might not be
>> maintained actively.
>>
>> Will think about how to handle this and come back here.
>>
>> Thanks,
>>
>> Michael Brohl
>>
>> ecomify GmbH - www.ecomify.de
>>
>>
>> [1] https://issues.apache.org/jira/browse/OFBIZ-12171
>>
>> PS: great to hear from you again, it's been a while, Taher.
>>
>>
>> Am 05.02.21 um 22:04 schrieb Taher Alkhateeb:
>>> 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

[Michael Brohl-3]

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.

Is anyone using the Ldap plugin and can help out to test the changes
I've made during the migration process?

If the community approves this solution I would go through the releases
and adapt this work to release 17.12 and 18.12 as well. I expect some
manual changes becaus of different dependencies (at least in versions).

Do we also want to adapt the changes to 16.11 even if not supported
anymore? We could provide a patch.

I'd also set up a wiki page to describe the problem and provide
informations for the different releases. The mentioned patch could go
there too.

Thoughts?

Thanks,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 06.02.21 um 13:52 schrieb Jacques Le Roux:

> That's a good news, thanks Michael
>
> Let's follow what we can expect from Infra, those guys often do marvel...
>
> Jacques
>
> Le 06/02/2021 à 11:42, Michael Brohl a écrit :
>> Infra is also at it, see
>> https://issues.apache.org/jira/browse/INFRA-21376
>>
>> Michael Brohl
>>
>> ecomify GmbH - www.ecomify.de
>>
>>
>> Am 06.02.21 um 11:29 schrieb Michael Brohl:
>>> Hi Taher,
>>>
>>> thanks for bringing this up!
>>>
>>> This is indeed something we should care about quite soon. It will
>>> affect the upcoming 18.12 release as well as supporting the 17.12
>>> release for which we might have to do another release handling this.
>>>
>>> I created a Jira issue for it at [1].
>>>
>>> I also did a first check with wiped Gradle cache and removed JCenter
>>> reference and put the results in the Jira as well. There are about
>>> 78 libraries which are not found at Maven central.
>>>
>>> While there are a lot of Apache libraries which we can assume to be
>>> moved to Maven central soon, there are also some libraries which
>>> might not be maintained actively.
>>>
>>> Will think about how to handle this and come back here.
>>>
>>> Thanks,
>>>
>>> Michael Brohl
>>>
>>> ecomify GmbH - www.ecomify.de
>>>
>>>
>>> [1] https://issues.apache.org/jira/browse/OFBIZ-12171
>>>
>>> PS: great to hear from you again, it's been a while, Taher.
>>>
>>>
>>> Am 05.02.21 um 22:04 schrieb Taher Alkhateeb:
>>>> 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
>

[Michael Brohl-3]

jFrog announced in an update that jCenter is going to serve artefacts
until February 1st 2022, see
https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

Regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 05.02.21 um 22:04 schrieb Taher Alkhateeb:

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

[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

[Jacques Le Roux]

It seems it does not concern Bintray itself, so what is described at
https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray
Will no longer be available

Jacques

Le 10/02/2021 à 11:17, Michael Brohl a écrit :

> jFrog announced in an update that jCenter is going to serve artefacts until February 1st 2022, see
> https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
>
> Regards,
>
> Michael Brohl
>
> ecomify GmbH - www.ecomify.de
>
>
> Am 05.02.21 um 22:04 schrieb Taher Alkhateeb:
>> 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
>>

[Michael Brohl-3]

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
>

[Michael Brohl-3]

Yes, this will cease soon. I think we'll have to move to mavenCentral
with this.

There is documentation about the process here:
https://maven.apache.org/repository/guide-central-repository-upload.html

Regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 10.02.21 um 16:24 schrieb Jacques Le Roux:

> It seems it does not concern Bintray itself, so what is described at
> https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray 
>
> Will no longer be available
>
> Jacques
>
> Le 10/02/2021 à 11:17, Michael Brohl a écrit :
>> jFrog announced in an update that jCenter is going to serve artefacts
>> until February 1st 2022, see
>> https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
>>
>> Regards,
>>
>> Michael Brohl
>>
>> ecomify GmbH - www.ecomify.de
>>
>>
>> Am 05.02.21 um 22:04 schrieb Taher Alkhateeb:
>>> 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
>>>

[Michael Brohl-3]

How to we sign in to the Bintray account? Who has the credentials for it?

Thanks,

Michael


Am 10.02.21 um 16:24 schrieb Jacques Le Roux:

> It seems it does not concern Bintray itself, so what is described at
> https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray 
>
> Will no longer be available
>
> Jacques
>
> Le 10/02/2021 à 11:17, Michael Brohl a écrit :
>> jFrog announced in an update that jCenter is going to serve artefacts
>> until February 1st 2022, see
>> https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
>>
>> Regards,
>>
>> Michael Brohl
>>
>> ecomify GmbH - www.ecomify.de
>>
>>
>> Am 05.02.21 um 22:04 schrieb Taher Alkhateeb:
>>> 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
>>>

[Jacques Le Roux]

It's in the private ML, please ask there ;)

Le 10/02/2021 à 16:55, Michael Brohl a écrit :

> How to we sign in to the Bintray account? Who has the credentials for it?
>
> Thanks,
>
> Michael
>
>
> Am 10.02.21 um 16:24 schrieb Jacques Le Roux:
>> It seems it does not concern Bintray itself, so what is described at
>> https://cwiki.apache.org/confluence/display/OFBIZ/Load+new+gradle+wrapper+version+on+bintray
>> Will no longer be available
>>
>> Jacques
>>
>> Le 10/02/2021 à 11:17, Michael Brohl a écrit :
>>> jFrog announced in an update that jCenter is going to serve artefacts until February 1st 2022, see
>>> https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
>>>
>>> Regards,
>>>
>>> Michael Brohl
>>>
>>> ecomify GmbH - www.ecomify.de
>>>
>>>
>>> Am 05.02.21 um 22:04 schrieb Taher Alkhateeb:
>>>> 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
>>>>

[Michael Brohl-3]

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

[Nicolas Malin-2]

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

[Michael Brohl-3]

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

[Nicolas Malin-2]

Hi Michael,

On 15/02/2021 22:12, Michael Brohl wrote:
> Hi Nicolas,
>
> I thought that we are restricted to the Gradle version for 17.12, aren‘t we?
Yes we said that. The rules are the better help to follow the path and
when it come to hard to follow perhaps it's time to share for an
alternative way.
> If not I think it‘s easy to upgrade Gradle to just the first version which supports metadataSources and proceed from there.

I think it's a good compromise to try :)

Nicolas

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

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