This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add info about uploading maven artifacts

...

Upload the artifacts to the apache nexus

Double check if your apache credentials are added to your local ~/.m2/settings.xml

Code Block
<settings>
  <server>
      <id>apache.snapshots.https</id>
      <username>your_apache_id</username>
      <password>your_apache_password</password>
    </server>
    <!-- To stage a release of some part of Maven -->
    <server>
      <id>apache.releases.https</id>
      <username>your_apache_id</username>
      <password>your_apache_password</password>
	 </server>
</settings>

Do a maven deploy from the ozone and hdds projects

Code Block
languagebash
themeRDark
titleUpload Release Artifacts
cd hadoop-ozone
mvn deploy
cd ../hadoop-hdds
mvn deploy

Go the the https://repository.apache.org and close the newly created hadoop repository (select the latest one which contains the hadoop in the name)

Image Added

Push the tag to github

Code Block
languagebash
themeRDark
titlePush the tag
git push origin ozone-0.4.0-alpha-RC0

...

And commit the artifacts to a new directory.

PMC members can move it to the final location:

Code Block
svn mv https://dist.apache.org/repos/dist/dev/hadoop/ozone-0.3.0-alpha https://dist.apache.org/repos/dist/release/hadoop/ozone/ozone-0.3.0-alpha

To publish the artifacts to the central maven, login to the https://repository.apache.org, select your staging repository and Release it.

Write a haiku

Check the tag from the Ozone Road Map page (it's a national park).

...