[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=17134465#comment-17134465 ] Hudson commented on MINSTALL-143: - Build succeeded in Jenkins: Maven TLP » maven-install-plugin » master #47 See https://builds.apache.org/job/maven-box/job/maven-install-plugin/job/master/47/ > 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 (v8.3.4#803005)
[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=16756734#comment-16756734 ] Christopher Tubbs commented on MINSTALL-143: [~beamerblvd], where do you see that recommendation "online"? Personally, I wouldn't recommend that. I just use maven-deploy-plugin and it works just fine when publishing to Sonatype Nexus repository manager staging repositories, and then use the UIs to close and/or release the repositories from there. I do not know what advantage nexus-staging-maven-plugin offers over maven-deploy-plugin, so perhaps there's some cool feature I'm missing out on... but I suspect not, since everything works just fine without it. > 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)
[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=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)
[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=16593000#comment-16593000 ] Hudson commented on MINSTALL-143: - Build succeeded in Jenkins: Maven TLP » maven-install-plugin » master #21 See https://builds.apache.org/job/maven-box/job/maven-install-plugin/job/master/21/ > 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 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > 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)
[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=16592998#comment-16592998 ] Karl Heinz Marbaise commented on MINSTALL-143: -- Done in [590e6108b7af7552b2ebfbc0838eb3560cad6d7b|https://gitbox.apache.org/repos/asf?p=maven-install-plugin.git;a=commitdiff;h=590e6108b7af7552b2ebfbc0838eb3560cad6d7b] > 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 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > 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)
[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=16575174#comment-16575174 ] Karl Heinz Marbaise commented on MINSTALL-143: -- [~Mikael Åsberg] It can't be done only in maven-install-plugin. This must be done at the same time in maven-deploy-plugin. Furthermore all integration tests needed to be checked and changed/fixed accordingly also getting green for maven-install-plugin https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-install-plugin/job/MSHARED-695/ as well as for maven-deploy-plugin: https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-deploy-plugin/job/MSHARED-695/ > 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 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > 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)
[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=16560183#comment-16560183 ] Mikael Åsberg commented on MINSTALL-143: maven-artifact-transfer 0.10.0 was released in the beginning of July, do we have have everything we need to complete this issue now? > 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 >Reporter: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > 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)
[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=16529470#comment-16529470 ] Karl Heinz Marbaise commented on MINSTALL-143: -- The maven-artifact-transfer component 0.10.0 implements this. Need to wait for release of 0.10.0 > 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 >Reporter: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > 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)
[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=16394284#comment-16394284 ] Karl Heinz Marbaise commented on MINSTALL-143: -- Hi Charles, this is only about the generation of the checksums which will be moved to the deploy plugin (or more accurate into artifact-transfer component). This has nothing to do with signing (see maven-gpg-plugin)...apart from that the ASF (Maven project also) does staging first but the staging of the artifacts includes already the checksums (md5, sha1) of the artifacts ...and Maven project uses GPG keys to sign artifacts which is also included during the staging (Take a look at the VOTE which is running on dev list)...furthermore the jira is not intended as discussion such things should be done on the dev mailing list... > 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 >Reporter: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > 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)
[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=16394282#comment-16394282 ] Charles Honton commented on MINSTALL-143: - Consider extracting checksums and signing into a separate plugin. Some organizations use their repository to stage, verify, and sign artifacts; no checksums are needed in this scenario. Some organizations also require public/private key signing; additional signing methods are needed in this scenario. advantages: * separation of concerns * flexibility to quickly add and configure new signing methods * availability of signing/checksuming non-artifacts short-term disadvantages: * additional default binding required in core maven * configuration is moving from install to signing plugin > 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 >Reporter: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > 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)
