[MDEPLOY-271] Allow to optionally disable checksum creation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 3.0.0-M1
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 08/Jun/20 12:19
• Updated: 17/Aug/20 12:20
• Resolved: 17/Aug/20 12:20

Description

Since 3.0.0-M1 the deploy goal will always generate SHA1/MD5 for all attached artifacts. The old configuration option https://maven.apache.org/plugins-archives/maven-install-plugin-2.4/install-mojo.html#createChecksum is no longer exposed in the maven-deploy-plugin. That leads to the fact the m-deploy-plugin 3.0.0-M1 will generate MD5/SHA1 even for attached SHA-512 artifacts (generated with https://checksum-maven-plugin.nicoulaj.net/artifacts-mojo.html) which are supported by Nexus since https://issues.sonatype.org/browse/NEXUS-21802.

It would be nice if one would be able to configure which artifacts (regex/glob on artifactId) should receive which hashes (algorithm).

That way generating only MD5 or SHA1 would be possible and also exclusion of checksums for certain attached artifacts.

Issue Links

• is related to: MDEPLOY-231 Move checksum generation from install to deploy plugin
• relates to: MRESOLVER-56 Support SHA-256 and SHA-512 as checksums
• relates to: MSHARED-922 Remove checksum creation from DefaultProjectDeployer
• relates to: SLING-7534 Release policy - stop providing MD5 and start providing SHA-512 checksums