Versions Compared

Old Version 8

changes.mady.by.user Chris Wilper

Saved on

compared with

New Version Current

changes.mady.by.user Chris Wilper

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

The CloudSync software is currently distributed via Maven Central, with the help of Sonatype's OSS Hosting.

On this page:

Table of Contents

Prerequisites

  • As a CloudSync committer, you should have permission to deploy to Sonatype. If you don't yet, create a Sonatype account for yourself, then contact an existing committer. Tell them your userid and ask them to request access on your behalf by submitting a comment to the DuraSpace hosting ticket at Sonatype.
  • Update your system-wide maven settings.xml file (usually found at ~/.m2) with your Sonatype credentials, like so:
    Code Block
    <settings>
  <servers>
    <server>
      <id>sonatype-nexus-snapshots</id>
      <username>YOUR-SONATYPE-USERNAME</username>
      <password>YOUR-SONATYPE-PASSWORD</password>
    </server>
    <server>
      <id>sonatype-nexus-staging</id>
      <username>YOUR-SONATYPE-USERNAME</username>
      <password>YOUR-SONATYPE-PASSWORD</password>
    </server>
    ..
  </servers>
  ..
</settings>
  • Make sure the KEYS file at the root of the source tree has your up to date public code signing key and signatures listed. If you don't yet have a code signing key, see Creating a Code Signing Key. When you are ready, append your key with the following command: (gpg --list-sigs YourKeyId && gpg -a --export YourKeyId) >> KEYS

Snapshot

...

Releases

A snapshot release can be performed any time via:

...

The artifacts will be immediately available at https://oss.sonatype.org/content/repositories/snapshots/org/duraspace/fcrepo-cloudsync

Official

...

Releases

First, stage the release (substitute the appropriate version number below).

...

CloudSync documentation is organized such that each feature release has its own wiki space, with an id named after that release. For example, CloudSync 1.0's space is CLOUDSYNC10. CloudSync 5.5's space would be CLOUDSYNC55. Bugfix releases don't trigger the creation of a new space. Instead, the details about the latest bugfix release are added to the appropriate feature releases's space. For example, CloudSync 1.0.1 would be discussed in the CLOUDSYNC10 space.

...