geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-781) Build does not publish signatures to maven
Date Sat, 16 Jan 2016 17:38:39 GMT


ASF subversion and git services commented on GEODE-781:

Commit 6b61d49266e074fec60c11ad08662bd81abbe345 in incubator-geode's branch refs/heads/develop
from [~amb]
[;h=6b61d49 ]

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

To upload the artifacts to Maven, you will need to set the following
properties in ~/.gradle/

> Build does not publish signatures to maven
> ------------------------------------------
>                 Key: GEODE-781
>                 URL:
>             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
> We should use the nexus plugin instead, see the samza approach at

This message was sent by Atlassian JIRA

View raw message