Yahav Itschak

Hey @donat, Appreciate you flagging this problem, and sorry for the delayed reply. Could you kindly inform us if you're encountering this issue in the most recent release, version 5.1.9?

Thanks for the information, @cpovirk. Are you interested in making a contribution by submitting a pull request to address this problem?

Hello @staffanf, Sorry for the late response. We have this functionality in the JFrog CLI, using `JFROG_CLI_MIN_CHECKSUM_DEPLOY_SIZE_KB` environment variable. Therefore I think it is reasonable to have it in the...

@staffanf, Gradle Artifactory plugin 4.18.2 is released. This release includes #408. Documentation will be updated soon. In order to force checksum download and make sure identical artifacts will not be...

@paul-hammant The Artifactory Maven and Gradle plugins compare either SHA1 and MD5 - an artifact does not upload if both SHA1 and MD5 exist in Artifactory.

> OK, an artifact does not upload if **both** SHA1 and MD5 exist in Artifactory **and are the same local and remote** Yes, exactly. > If the artifact exists in...

Hi @DanielJRutledge version 5.0.1 includes https://github.com/jfrog/artifactory-gradle-plugin/pull/32 which should help mitigating this issue. Do you still encounter issues in 5.0.1?

@davidnelson-hms, ~The Gradle Artifactory plugin collects the build info **during** build. In other words, we get the information about artifacts and dependencies only when Gradle downloads dependencies and builds the...

Thanks for your valuable feedback, @davidnelson-hms @staffanf. We are taking it seriously and working diligently on resolving this issue for you. We'll keep you updated.

@davidnelson-hms @staffanf Update - I created this [PR](https://github.com/jfrog/build-info/pull/390) to target the issue. The change forces previous outputs of extractModuleInfo to not be reused, so that this task will never be...