Hi Jacques
It seems, for now, it has again started working, so no need for changes.
But I am keeping an eye on this because in another thread Daniel also faced
the same issue. I am unsure if anything was done by the spring community.
All of our docker based builds in all environments were
Thanks Girish,
Reluctant to clean all my cache (1 GB to download again for the 3 branches), I have tried 1st to manually remove only but all the syndication files in
cache to no avail. I mean the files where put back when building.
I then used --refresh-dependencies, the build worked too.
Hi Jacques,
Yes, I do. Apparently, the artifact "
com.sun.syndication:com.springsource.com.sun.syndication:1.0.0" is
available on "https://plugins.gradle.org/m2/; too. I was able to do a
successful build using this.
Earlier, the syndication dependency was being resolved from "
Le 27/07/2021 à 15:47, Girish Vasmatkar a écrit :
Possibly, gradle cache is preventing building failure but if you do clean
up your cache you should start getting build failure. Can someone please
confirm?
Hi Girish,
Before doing so, do you have a cure?
Jacques
Hello All,
Has anyone also started noticing build failure due to repo.spring.io that
OFBiz uses for "com.springsource.com.sun.syndication"?
Here's the relevant details :
https://spring.io/blog/2020/10/29/notice-of-permissions-changes-to-repo-spring-io-fall-and-winter-2020
Possibly, gradle cache
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*
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
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
+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.
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
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
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
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:
Done
Le 16/02/2021 à 10:33, Michael Brohl a écrit :
Can someone please create a 17.12.06 release version in Jira?
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
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 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
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 :
>
> Hi Michel,
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
>
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
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
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
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
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
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
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
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
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
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
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
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
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
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:
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
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
35 matches
Mail list logo
