Re: [GH] (ofbiz-framework): Workflow run "Java CI with Gradle" failed!

2024-02-06 Thread Jacques Le Roux
Hi, With https://ci2.apache.org/#/builders/46/builds/647 I tried to remove a file from nightlies but that does not work anyway: <> So seems you can copy but not remove a file. Anyway, I have put back the previous ofbiz.py version (BB config) and rebuilt again. I have asked Infra to remove

Re: [GH] (ofbiz-framework): Workflow run "Java CI with Gradle" failed!

2024-02-05 Thread Jacques Le Roux
I pushed a fix but BB is still blocked Le 05/02/2024 à 15:02, Michael Brohl a écrit : I see the problem: I have not had the plugins embedded during the test so the setMaxPriority3Violations were not exceeded. Thanks, Michael Am 05.02.24 um 12:55 schrieb Jacques Le Roux: If you compare the

Re: [GH] (ofbiz-framework): Workflow run "Java CI with Gradle" failed!

2024-02-05 Thread Michael Brohl
I see the problem: I have not had the plugins embedded during the test so the setMaxPriority3Violations were not exceeded. Thanks, Michael Am 05.02.24 um 12:55 schrieb Jacques Le Roux: If you compare the last in nightlies: https://nightlies.apache.org/ofbiz/trunk/codenarc.html with the last

Re: [GH] (ofbiz-framework): Workflow run "Java CI with Gradle" failed!

2024-02-05 Thread Jacques Le Roux
If you compare the last in nightlies: https://nightlies.apache.org/ofbiz/trunk/codenarc.html with the last locally, it's 3 priorities 3 (SpaceAfterOpeningBrace) in fixedasset package at line 144 of FixedAssetServices.groovy So we pass from setMaxPriority3Violations(3979) in Gradle to 3982 with

Re: [GH] (ofbiz-framework): Workflow run "Java CI with Gradle" failed!

2024-02-05 Thread Michael Brohl
The build says that there are CodeNarc rule violations found but when I locally run ./gradlew codenarcMain codenarcTest I got no errors. Is there a way to view the check results in buildbot? Regards, Michael Brohl ecomify GmbH - www.ecomify.de Am 05.02.24 um 10:21 schrieb GitBox: The

Re: [GH] (ofbiz-framework): Workflow run "Java CI with Gradle" failed!

2023-12-05 Thread Jacques Le Roux
As we know: << GitHub has temporarily disabled Subversion support as part of a planned brownout 64 in order to give you advance notice of the upcoming permanent removal of 65