[
https://issues.apache.org/jira/browse/RYA-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047417#comment-15047417
]
David W. Lotts commented on RYA-16:
---
h1. What to do for Rya:
This is customized and summarized from the Apache specific instructions:
http://www.apache.org/dev/publishing-maven-artifacts.html
h2. Releases go
www.apache.org/dist/ -- required
repository.apache.org-- an optional convenience, but the subject of this
task
Central repo -- consequentially (automatically?)
h2. Steps to setup
# Create a [JIRA ticket using this fancy URL|
https://issues.apache.org/jira/secure/CreateIssueDetails!init.jspa?issuetype=3=3=10410=12312660=Enable+Nexus+Access+For+Apache+Rya=Project+URL:%0D%0DSVN+URL:%0D%0DMaven+Group+Ids:+org.apache.rya%0D%0D+a+TLP+Project:]
(<-- click this link) with the following information:
- Project URL: http://rya.apache.org
- SVN URL: where the source is located in case we need to lookup more
information and to provide feedback on your pom.
https://github.com/apache/incubator-rya
- Maven Group Ids:
org.apache.rya
- Managed By This TLP Project: Rya is a TLP
Once this JIRA is filed, the following will happen:
- Setup the project in the ASF Nexus: We will configure your groupIds in
Nexus and link them to the appropriate LDAP group for Authorization
- Move Existing Artifacts: In order to maintain the proper
maven-metadata.xml files and to prevent rsync conflicts in Central, we must
move all your artifacts to the new repository. We will move your artifacts from
the old repository on people to the new repository and mark the folder in
people as read-only to prevent accidental deployments.
- Check POM's: We will quickly check your POM (if your project is Maven
based) for any obvious problems. If you have specific questions or concerns,
please call them out in the issue.
# All artifacts must be signed with a key that is publicly verifiable. Follow
the instructions here to get your keys created and environment setup.
https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
http://maven.apache.org/guides/mini/guide-encryption.html
# Modify the pom.xml and settings.xml
# Test your settings
Try installing locally artifacts with activation apache-release profile.
mvn clean install -Papache-release (this will build artifacts, sources and
sign)
# Stage a release
Done, [detailed instructions
here|http://www.apache.org/dev/publishing-maven-artifacts.html]
> Build and Deploy to ASF and Maven Central Repository
> -
>
> Key: RYA-16
> URL: https://issues.apache.org/jira/browse/RYA-16
> Project: Rya
> Issue Type: Task
>Affects Versions: 3.2.10
> Environment: Rya project's pom.xml, repository.apache.org,
> repo1.maven.org/maven2
>Reporter: David W. Lotts
> Labels: build, maven
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Setup all the required configuration, permissions, and keys for deploying
> releases to the ASF snapshot and release repositories, which synchronizes to
> the Central Repository.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
