Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 526074

Summary:	Eclipse Ditto would like to publish to Maven Central
Product:	Community	Reporter:	Thomas J??ckle <thomas.jaeckle>
Component:	CI-Jenkins	Assignee:	CI Admin Inbox <ci.admin-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	frederic.gurr, webmaster
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows NT
Whiteboard:

Description Thomas J??ckle

2017-10-16 06:34:47 EDT

Eclipse Ditto would like to publish to Maven Central using the JIPP instance https://ci.eclipse.org/ditto/.
As I understood we'd need a OSSRH account and a GPG key which are created by the Webmaster and we committer will sign the GPG key with our private keys.

Could you create the keypair and configure the Maven settings.xml on our JIPP instance accordingly?

I already created a user in Sonatype's OSSRH for access to the OSSRH staging repository, username: "thjaeckle"

Thanks in advance.

Best regards
Thomas

Comment 1 Thomas J??ckle

2017-10-19 05:15:46 EDT

Username "kartben" should also get access permissions.

Comment 2 Frederic Gurr

2017-10-24 05:19:48 EDT

OSSRH ticket has been created (https://issues.sonatype.org/browse/OSSRH-35442).

Once this ticket is resolved, we will set up the GPG keys and the JIPP.

Comment 3 Frederic Gurr

2017-10-25 05:21:11 EDT

https://issues.sonatype.org/browse/OSSRH-35442 is now resolved.

The signing key on your JIPP has also been created and configured. Your public key is https://pgp.mit.edu/pks/lookup?op=vindex&search=0x83152FB003D7A0D6 It is signed by the webmaster's key. As a committer, you should sign it too.

You have to use dedicated Maven settings for deployments to OSSRH. These settings have to be selected in the Maven build step in your jobs (under Advanced). Switch "Settings file" from "Use default maven settings" to "Settings file in filesystem" and enter the following path:

/opt/public/hipp/homes/genie.ditto/.m2/settings-deploy-ossrh.xml

The settings contain a server definition named 'ossrh' to let you upload things to Sonatype's server. This server id should be used in a distributionManagement repository somewhere specifying the URL. See http://central.sonatype.org/pages/ossrh-guide.html#releasing-to-central and http://central.sonatype.org/pages/ossrh-guide.html#ossrh-usage-notes for details.

The GPG passphrase is also configured (encrypted) in the settings (as described at https://maven.apache.org/plugins/maven-gpg-plugin/usage.html#Configure_passphrase_in_settings.xml). You can now use the maven-gpg-plugin, it should work as is without further configuration if you have properly selected the dedicated OSSRH Maven settings file.

Let us know when you promoted your first release so we can comment on
https://issues.sonatype.org/browse/OSSRH-35442. Or you can do this yourself.