[
https://issues.apache.org/jira/browse/MDEPLOY-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128615#comment-17128615
]
Konrad Windszus commented on MDEPLOY-271:
-----------------------------------------
Maven Resolver does not yet support creating SHA512/SHA256 checksums. Therefore
I currently have to use a different plugin for that. Also the MD5/SHA1 support
in the m-deploy-plugin (MDEPLOY-231) is part of the
https://github.com/apache/maven-artifact-transfer/blob/d4df3387215336eb52358f054e742ad44ad9e88f/src/main/java/org/apache/maven/shared/transfer/project/deploy/internal/DefaultProjectDeployer.java#L130
but not of the Maven Resolver!
> Allow to optionally disable checksum creation
> ---------------------------------------------
>
> Key: MDEPLOY-271
> URL: https://issues.apache.org/jira/browse/MDEPLOY-271
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Affects Versions: 3.0.0-M1
> Reporter: Konrad Windszus
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
