[jira] [Resolved] (INFRA-8882) Apache Ambari - Publish to Central Repository

["Brian Fox (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-8882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox resolved INFRA-8882.
------------------------------
    Resolution: Fixed

I went ahead and configured you in Nexus. Follow the rest of the instructions in the document David linked and your stuff will get published to Central.

[INFO] Repository 'snapshots' already exists, won't create a new one.
[INFO] Repository 'releases' already exists, won't create a new one.
[INFO] Reporitory Group 'public' already exists, won't create a new one.
[INFO] Reporitory Group 'staging' already exists, won't create a new one.
[INFO] Repository Target 'org.apache.ambari' is created.
[INFO] Staging Profile 'org.apache.ambari' is created.
[INFO] Privileges (CRU) 'org.apache.ambari - Public Repositories' are created.
[INFO] Privileges (CRUD) 'org.apache.ambari - Snapshots' are created.
[INFO] Role 'org.apache.ambari Deployment Role' is created.
[WARNING] No user specified.
-- Nexus repository was prepared successfully. --

Configuration has been prepared, now you can:
* Deploy snapshot artifacts into repository https://repository.apache.org/content/repositories/snapshots
* Deploy release artifacts into the staging repository https://repository.apache.org/service/local/staging/deploy/maven2
* Promote staged artifacts into repository 'Releases'
* Download snapshot and release artifacts from group https://repository.apache.org/content/groups/public
* Download snapshot, release and staged artifacts from staging group https://repository.apache.org/content/groups/staging


> Apache Ambari - Publish to Central Repository
> ---------------------------------------------
>
>                 Key: INFRA-8882
>                 URL: https://issues.apache.org/jira/browse/INFRA-8882
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Nexus
>            Reporter: Alejandro Fernandez
>
> To whom it may concern,
> I'm one of the committers for the Ambari project (http://ambari.apache.org/) and we would like to upload build artifacts to a central repository.
> Can you help with this?
> We've already followed the steps in http://maven.apache.org/guides/mini/guide-central-repository-upload.html
> so that the pom file has all of the needed information.
> https://github.com/apache/ambari/blob/trunk/ambari-views/pom.xml
> has the following,
> {code}
>     <groupId>org.apache.ambari</groupId>
>     <artifactId>ambari-views</artifactId>
>     <packaging>jar</packaging>
>     <name>Ambari Views</name>
>     <version>1.3.0-SNAPSHOT</version>
>     <description>Ambari View interfaces.</description>
>     <url>http://ambari.apache.org/</url>
>     <scm>
>       <url>https://github.com/apache/ambari</url>
>       <connection>https://git-wip-us.apache.org/repos/asf/ambari.git</connection>
>     </scm>
> {code}
> And its effective pom file has the "Apache License, Version 2.0" information.
> We only need to do this for the ambari-views project and its artifacts, which I've uploaded and already signed here.
> http://people.apache.org/~alejandro/ambari-views-1.7.0.0/
> Import key,
> gpg --keyserver hkp://pgp.mit.edu --recv-keys 392F57AC
> My key trust,
> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x392F57AC 
> Verify files, 
> gpg --verify ambari-views-1.7.0.0.jar.asc
> gpg --verify ambari-views-1.7.0.0-sources.jar.asc
> gpg --verify ambari-views-1.7.0.0-javadoc.jar.asc
> I sent an email to repo-maintainers@maven.apache.org on Dec 1 with this same information.
> Thanks,
> Alejandro Fernandez



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)