Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 533616 - Configure EMF JIPP for Maven Central
Summary: Configure EMF JIPP for Maven Central
Status: CLOSED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: CI Admin Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 529613
  Show dependency tree
 
Reported: 2018-04-16 10:00 EDT by Karsten Thoms CLA
Modified: 2018-04-18 05:35 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Thoms CLA 2018-04-16 10:00:23 EDT
bug#529613 is requesting publishing of EMF artifacts to Maven Central. Recently EMF builds have moved to JIPP https://ci.eclipse.org/emf/. This JIPP instance needs to be configured for deployment (as described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=528797#c9).
Comment 1 Frederic Gurr CLA 2018-04-17 12:07:44 EDT
https://issues.sonatype.org/browse/OSSRH-39222 is now resolved.

The signing key on your JIPP has also been created and configured. Your public key is http://keys.gnupg.net/pks/lookup?op=vindex&search=0x5492CB8CE546E049. 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.emf/.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-39222. Or you can do this yourself.
Comment 2 Karsten Thoms CLA 2018-04-18 02:55:43 EDT
The link to the public key does not work.
Comment 3 Frederic Gurr CLA 2018-04-18 05:02:31 EDT
(In reply to Karsten Thoms from comment #2)
> The link to the public key does not work.

The server is down. PGP key servers are far from reliable these days.

Please try http://hkps.pool.sks-keyservers.net/pks/lookup?op=vindex&search=0x5492CB8CE546E049 instead.
Comment 4 Ed Merks CLA 2018-04-18 05:03:39 EDT
FYI, that failed for me the same way:

Not Found

The requested URL /pks/lookup was not found on this server.
Apache/2.4.10 (Debian) Server at hkps.pool.sks-keyservers.net Port 80
Comment 5 Frederic Gurr CLA 2018-04-18 05:35:05 EDT
*sigh* Works fine for me.

Since this is only a frontend for a pool of servers, I guess you were redirected to a bad one.

Here are a few alternative links:
https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5492CB8CE546E049
https://sks-keyservers.net/overview-of-pools.php

You can also search for "Eclipse EMF" on a keyserver to find the public key.