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 <nicolas.ma...@nereide.fr>: > > 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 >>>>
