maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MGPG-27) Allow option to create none ascii output
Date Sun, 25 Jul 2010 17:02:32 GMT

    [ http://jira.codehaus.org/browse/MGPG-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229773#action_229773
] 

Benjamin Bentmann commented on MGPG-27:
---------------------------------------

So to double-check, your legacy build merely needs to deploy binary signatures along the project
artifacts?

bq. Keeping the same extension .asc will keep minimal change to gpg plugin
I don't think it's a good idea to mess with established conventions regarding the file extension
and the implied content type. To my knowledge {{.sig}} is the extension usually used for binary
signatures, so we should use that.

> Allow option to create none ascii output
> ----------------------------------------
>
>                 Key: MGPG-27
>                 URL: http://jira.codehaus.org/browse/MGPG-27
>             Project: Maven 2.x GPG Plugin
>          Issue Type: New Feature
>    Affects Versions: 1.1
>         Environment: all
>            Reporter: Dan Tran
>
> Please add new option "armor" with default value "true" to keep the default behavior.
> The motivation is i am currently have a sh script using gpg and expect the produce a
binary gpg file.  It would be nice for me to use maven-gpg-plugin intead

-- 
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

        

Mime
View raw message