geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-781) Build does not publish signatures to maven
Date Sat, 06 Feb 2016 18:07:40 GMT

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

Mime
View raw message