[
https://issues.apache.org/jira/browse/YETUS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393679#comment-15393679
]
Sean Busbey edited comment on YETUS-406 at 7/26/16 11:56 AM:
-------------------------------------------------------------
I'll be publishing 0.3.0 artifacts when I get back to my signing machine in ~12
hours. If any of the PMC members have access to their signing keys and would
like to take care of that step before then, I'd appreciate it.
I believe the steps are like this:
# Set up maven to allow deploys to ASF nexus. This requires modifying
{{~/.m2/settings.xml}} so that you can authenticate to the ASF nexus and sign
jars during the build. I can't find a good infra doc on this, but [commons has
some
instructions|https://wiki.apache.org/commons/UsingNexus#Preparations_for_using_Nexus]
and [hbase has some
instructions|http://hbase.apache.org/book.html#maven.settings.xml].
# download the source release artifact. It's important that the artifacts
deployed to nexus be generated off of our official release tarball. It has to
be the one we voted on, and not just the source tag.
[downloads|http://www.apache.org/dist/yetus/]
# Use maven to stage artifacts. Essentially this is running a maven deploy.
{code}
mvn -Papache-release deploy
{code}
# Examine staged build. Go to [the ASF
repository|http://repository.apache.org/] and log in with your asf LDAP
credentials. Look for the staging repository with a name that includes "yetus".
Clicking on it will give you a link to an "open" repository. You can examine
the structure in the nexus api while you're logged in. If it looks essentially
correct, "close" the repository. This will give you a link that other folks can
use to interact with the repository. If you like, post it here for review.
# Publish the repository. Select the closed repository and use the "release"
button to publish the artifacts to the official ASF repo, which will then
mirror to central.
was (Author: busbey):
I'll be publishing 0.3.0 artifacts when I get back to my signing machine in ~12
hours. If any of the PMC members have access to their signing keys and would
like to take care of that step before then, I'd appreciate it.
I believe the steps are like this:
# Set up maven to allow deploys to ASF nexus. This requires modifying
`~/.m2/settings.xml` so that you can authenticate to the ASF nexus and sign
jars during the build. I can't find a good infra doc on this, but [commons has
some
instructions|https://wiki.apache.org/commons/UsingNexus#Preparations_for_using_Nexus]
and [hbase has some
instructions|http://hbase.apache.org/book.html#maven.settings.xml].
# download the source release artifact. It's important that the artifacts
deployed to nexus be generated off of our official release tarball. It has to
be the one we voted on, and not just the source tag.
[downloads|http://www.apache.org/dist/yetus/]
# Use maven to stage artifacts. Essentially this is running a maven deploy.
{code}
mvn -Papache-release deploy
{code}
# Examine staged build. Go to [the ASF
repository|http://repository.apache.org/] and log in with your asf LDAP
credentials. Look for the staging repository with a name that includes "yetus".
Clicking on it will give you a link to an "open" repository. You can examine
the structure in the nexus api while you're logged in. If it looks essentially
correct, "close" the repository. This will give you a link that other folks can
use to interact with the repository. If you like, post it here for review.
# Publish the repository. Select the closed repository and use the "release"
button to publish the artifacts to the official ASF repo, which will then
mirror to central.
> Publish Yetus Audience Annotations to Maven Central/JCenter
> -----------------------------------------------------------
>
> Key: YETUS-406
> URL: https://issues.apache.org/jira/browse/YETUS-406
> Project: Yetus
> Issue Type: Improvement
> Components: Audience Annotations, website and documentation
> Reporter: Michael Kobit
> Assignee: Sean Busbey
> Priority: Minor
>
> I don't see the Audience annotations available on any public binary
> repository.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
