Details
-
Improvement
-
Resolution: Done
-
Major
-
None
-
3.0.0
-
None
Description
Gradle can deploy sha256/sha512 checksum files along with it's content, we should make sure those files can be stored properly, as well as regenerating those files, when we rebuild metadata. Problem arises when we rebuild maven metadata, the sha256/sha512 files will be ignored and ultimately no longer have proper checksums when the metadata is rebuilt.
Note NXRM2 counterpart NEXUS-21802
Attachments
Issue Links
- is related to
-
NEXUS-21802 Maven metadata sha256/sha512 checksum considerations in staging
-
- Closed
-
-
NEXUS-25147 Rebuild metadata task leaves sha256 and sha512 files untouched for metadata files
-
- Closed
-
-
NEXUS-27104 Rebuild checksums option in maven metadata rebuild should create sha512 and sha256 checksums
-
- Closed
-