[
http://jira.codehaus.org/browse/MINSTALL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217864#action_217864
]
SebbASF commented on MINSTALL-74:
---------------------------------
Sorry, did not realise that the deploy plugin creates hashes.
Before re-opening the issue, I had a look at the Maven deploy plugin
documentation, and did not notice any reference to it creating checksums. I've
just had another look, and still cannot find any documentation to say that it
creates checksums.
The only reference I could find to hashes is:
bq. As a repository contains more than the artifacts (POMs, the metadata, MD5
and SHA1 hash files...), deploying means not only copying the artifacts
which suggests that the hashes are generated elsewhere and merely copied by the
plugin.
> CLONE -Don't create checksums for gpg signature files
> -----------------------------------------------------
>
> Key: MINSTALL-74
> URL: http://jira.codehaus.org/browse/MINSTALL-74
> Project: Maven 2.x Install Plugin
> Issue Type: Improvement
> Affects Versions: 2.2
> Reporter: SebbASF
> Assignee: Benjamin Bentmann
> Priority: Minor
>
> If the gpg plugin is configured and the install plugin configured to create
> checksums - then it ends up creating checksums for the signature files as
> well as the actual artifacts being installed.
> Attaching a patch which stops checksums being created for files ending in
> ".asc"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
