[jira] [Commented] (THRIFT-1114) Maven publish shouldn't require passwords hardcoded in settings.xml
[ https://issues.apache.org/jira/browse/THRIFT-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022244#comment-13022244 ] Hudson commented on THRIFT-1114: Integrated in Thrift #134 (See [https://builds.apache.org/hudson/job/Thrift/134/]) > Maven publish shouldn't require passwords hardcoded in settings.xml > --- > > Key: THRIFT-1114 > URL: https://issues.apache.org/jira/browse/THRIFT-1114 > Project: Thrift > Issue Type: Improvement >Reporter: Bryan Duxbury >Assignee: Jake Farrell > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (THRIFT-1114) Maven publish shouldn't require passwords hardcoded in settings.xml
[ https://issues.apache.org/jira/browse/THRIFT-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022208#comment-13022208 ] Jake Farrell commented on THRIFT-1114: -- Current maven gpg plugin does not support encrypted passwords in the ~/.m2/settings.xml file. Ticket: http://jira.codehaus.org/browse/MGPG-31. Looking into what it would take for me to add this to the gpg plugin > Maven publish shouldn't require passwords hardcoded in settings.xml > --- > > Key: THRIFT-1114 > URL: https://issues.apache.org/jira/browse/THRIFT-1114 > Project: Thrift > Issue Type: Improvement >Reporter: Bryan Duxbury >Assignee: Jake Farrell > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira