You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nick Williams (JIRA)" <ji...@apache.org> on 2019/01/20 06:22:00 UTC
[jira] [Commented] (MINSTALL-143) Move checksum generation from
install to deploy plugin
[ https://issues.apache.org/jira/browse/MINSTALL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747377#comment-16747377 ]
Nick Williams commented on MINSTALL-143:
----------------------------------------
Any suggestions on how to get artifact checksums when using {{org.sonatype.plugins:nexus-staging-maven-plugin}} plugin instead of {{org.apache.maven.plugins:maven-deploy-plugin}} to manage deploys? The recommendation online is to use the Sonatype plugin instead of the built-in Deploy plugin whenever publishing to Sonatype repositories (which includes Maven Central), but that seems to eliminate checksums.
> Move checksum generation from install to deploy plugin
> ------------------------------------------------------
>
> Key: MINSTALL-143
> URL: https://issues.apache.org/jira/browse/MINSTALL-143
> Project: Maven Install 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
>
>
> We should move the checksum generation from maven-install-plugin to maven-deploy-plugin cause the checksums will only be needed as a preparation for the transfer to a remote repository but not for an installation into a local repository.
> This needed to be done within maven-artifact-transfer component first.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)