[GRADLE-3303] Incorrect checksums generated for artefacts published to S3 Created: 25/May/15 Updated: 23/Jun/15 Resolved: 26/May/15 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 2.4 |
| Fix Version/s: | 2.5-rc-1 |
| Type: | Bug | ||
| Reporter: | Adrian Kelly (Inactive) | Assignee: | Adrian Kelly (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Known Issue Of: |
| Description |
|
The maven-publish plugin is uploading incorrect md5 and sha1 checksums for primary artifacts. This [sample project](https://github.com/adrianbk/s3-checksums) reproduces the issue whereby the checksums published via HTTP are correct but the checksums published via S3 are incorrect. See: https://discuss.gradle.org/t/wrong-checksums-when-uploading-to-s3-repo-with-maven-publish-plugin |
| Comments |
| Comment by Adrian Kelly (Inactive) [ 26/May/15 ] |
|
Fixed via the replacement of maven ant tasks with Maven 3/aether libraries. |