[
https://issues.apache.org/jira/browse/MDEPLOY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128416#comment-17128416
]
Konrad Windszus commented on MDEPLOY-231:
-----------------------------------------
Just for the record, prior to 3.0.0-M1 the MD5 and SHA1 checksums also have
been created via
https://github.com/apache/maven-deploy-plugin/blob/3b62d2a0bd33119194f5605ea0d281652c7d934f/src/main/java/org/apache/maven/plugin/deploy/AbstractDeployMojo.java#L171
->
https://github.com/apache/maven-artifact/blob/ab6be5e8c9d05f20dd37f813063482493788d1e9/src/main/java/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java#L109
->
https://github.com/apache/maven/blob/a2b800de32cdb9adc1e64a43a0fc32e3ba878103/maven-compat/src/main/java/org/apache/maven/repository/legacy/DefaultWagonManager.java#L634
> Move checksum generation from install to deploy plugin
> ------------------------------------------------------
>
> Key: MDEPLOY-231
> URL: https://issues.apache.org/jira/browse/MDEPLOY-231
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Affects Versions: 3.0.0-M1
> Reporter: Karl Heinz Marbaise
> Assignee: Karl Heinz Marbaise
> Priority: Blocker
> Fix For: 3.0.0-M1
>
>
> It is need to consistently move the checksum generation into
> maven-deploy-plugin which means to change the maven-artifact-transfer
> component accordingly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
