How to confirm the <downloadRetries> option within pom.xml is working

[timdachtera]

Hello, I was forwarded to this space from the MBT team in hopes to find my answer.

We have added in the   <downloadRetries> 10 </downloadRetries> to our pom.xml file, however even when attempting to call a known-invalid URL, I do not see any sort of retry responses in our logging:

09:23:34 info mtaBuild - [INFO]
09:23:34 info mtaBuild - [INFO] --- cds:2.4.0:install-node (cds.install-node) @ cisco ---
09:23:34 info mtaBuild - [INFO] InstallNodeMojo: Installing Node.js v18.18.2
09:23:34 info mtaBuild - [INFO] InstallNodeMojo: Downloading https://localhost/v18.18.2/node-v18.18.2-linux-x64.tar.gz to /home/mta/.m2/repository/com/sap/cds/cds-maven-plugin/cache/archive/18.18.2/archive-18.18.2-linux-x64.tar.gz
09:23:34 info mtaBuild - [INFO] InstallNodeMojo: No proxy was configured, downloading directly.
09:23:34 info mtaBuild - Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
09:23:34 error mtaBuild - [ERROR] InstallNodeMojo: The archive /home/mta/.m2/repository/com/sap/cds/cds-maven-plugin/cache/archive/18.18.2/archive-18.18.2-linux-x64.tar.gz is corrupted and will be deleted. Please try the build again.

How can I confirm that we are indeed retrying the download attempt?  I understand the 'default' retry is 3 times, but I see no logged/output retries when attempting to download.

I'm available for chatting on slack or teams to help expedite this, as this issue has been open since Nov. of 2023 getting passed around to different team.

We are leveraging this within our Java/CAP builds with a Jenkins/Hyperspace pipeline configuration.