[
https://issues.apache.org/jira/browse/MDEPLOY-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178935#comment-17178935
]
Konrad Windszus edited comment on MDEPLOY-271 at 8/17/20, 11:58 AM:
--------------------------------------------------------------------
With MSHARED-922 being implemented we can close this one as invalid.
[~michael-o] As I don't have the karma to close my own issues, can you do that?
was (Author: kwin):
With MSHARED-922 being implemented we can close this one as invalid.
> 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
> Fix For: waiting-for-feedback
>
>
> 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)
