Return-Path: X-Original-To: apmail-geode-issues-archive@minotaur.apache.org Delivered-To: apmail-geode-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 78A7A18E44 for ; Sat, 6 Feb 2016 18:07:41 +0000 (UTC) Received: (qmail 4208 invoked by uid 500); 6 Feb 2016 18:07:41 -0000 Delivered-To: apmail-geode-issues-archive@geode.apache.org Received: (qmail 4176 invoked by uid 500); 6 Feb 2016 18:07:41 -0000 Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.incubator.apache.org Delivered-To: mailing list issues@geode.incubator.apache.org Received: (qmail 4167 invoked by uid 99); 6 Feb 2016 18:07:41 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Feb 2016 18:07:41 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id F0FD51A05E1 for ; Sat, 6 Feb 2016 18:07:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.649 X-Spam-Level: X-Spam-Status: No, score=-3.649 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.429] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id p3YjeJH8jNtk for ; Sat, 6 Feb 2016 18:07:40 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 5463520CDE for ; Sat, 6 Feb 2016 18:07:40 +0000 (UTC) Received: (qmail 3942 invoked by uid 99); 6 Feb 2016 18:07:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Feb 2016 18:07:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0B6DA2C1F5C for ; Sat, 6 Feb 2016 18:07:40 +0000 (UTC) Date: Sat, 6 Feb 2016 18:07:40 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: issues@geode.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (GEODE-781) Build does not publish signatures to maven MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/GEODE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135910#comment-15135910 ] ASF subversion and git services commented on GEODE-781: ------------------------------------------------------- Commit e9bf2535fcd635bc183123138e1a8b28501f4374 in incubator-geode's branch refs/heads/develop from [~amb] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=e9bf253 ] GEODE-781: Update maven publishing to include signatures The maven-publish plugin does not grok signature nor sign pom files. These are needed for publishing release versions on Maven Central. Switching over to the nexus plugin simplified signing, generation of javadoc / sources jars, and publishing. To publish to the local maven repository (~/.m2/repository): gradle install To publish to the snapshot / release repositories: gradle uploadArtifacts Signatures will only be created if the following properties are set in ~/.gradle.properties: signing.keyId signing.secretKeyRingFile signing.password To upload the artifacts to Maven, you will need to set the following properties in ~/.gradle/gradle.properties: nexusUsername nexusPassword > Build does not publish signatures to maven > ------------------------------------------ > > Key: GEODE-781 > URL: https://issues.apache.org/jira/browse/GEODE-781 > Project: Geode > Issue Type: Bug > Components: build > Reporter: Anthony Baker > Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > > We have been using the maven-publish plugin in our build to publish build artifacts to maven repositories. Unfortunately this has some limitations when used for release builds as it is incapable of signing poms or uploaded signature files (see https://issues.gradle.org/browse/GRADLE-3183). > We should use the nexus plugin instead, see the samza approach at https://github.com/apache/samza/blob/master/gradle/release.gradle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)