[jira] [Closed] (MDEPLOY-199) Ability to set properties containing the SNAPSHOT id and hash information assigned by repository.

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MDEPLOY-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MDEPLOY-199.
----------------------------------
    Resolution: Won't Fix

This cannot be solve here. Checksums are completely opaque to this plugin. They are solely created by MRESOLVER and are an implementation detail to avoid bitrot during transport. Consider using the https://github.com/nicoulaj/checksum-maven-plugin. All checksum handling has been removed in 3.0.0.

> Ability to set properties containing the SNAPSHOT id and hash information assigned by repository.
> -------------------------------------------------------------------------------------------------
>
>                 Key: MDEPLOY-199
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-199
>             Project: Maven Deploy Plugin
>          Issue Type: New Feature
>          Components: deploy:deploy
>    Affects Versions: 2.8.2
>            Reporter: Jeff Vincent
>            Priority: Minor
>
> I'm building a continuous deployment pipeline with Jenkins and GoCD and when SNAPSHOT artifacts are published, I want to trigger the pipeline with the EXACT SNAPSHOT version generated by the deploy to Nexus (or equivalent) in order to make our deployment pipelines.
> In our case we are using SaltStack to provision our systems and we are pulling the WAR file directly from Nexus as a 'managed file' in saltstack.  It needs the SHA1 or MD5 hash for files hosted externally to be able to detect changes.
> I'd like a way to be able to retrieve the SNAPSHOT version and the SHA1 (and maybe MD5) hash of the artifact and be able to write them to a file or  set environment variables. 
> I'm not versed in Maven to know exactly what is possible in this regard since things like resource filtering happens before the build and this is after the build has been published.
> Regardless, the hope would be to get that data as part of the build process to be used on steps later in the CI/CD pipeline process.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)