Versions Compared

Old Version 11

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 12

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <servers>
    <!--Login info for Sonatype SnapShot repository-->
    <server>
      <id>sonatype-nexus-snapshots</id>
      <username>YourUsername<<username>YourSonatypeUsername</username>
      <password>YourPassword<<password>YourSonatypePassword</password>
    </server>
    <!--Login info for Sonatype Staging/Release repository-->
    <server>
      <id>sonatype-nexus-staging</id>
      <username>YourUsername<<username>YourSonatypeUsername</username>
      <password>YourPassword<<password>YourSonatypePassword</password>
    </server>
    <!--Login info for DSpace Projects (projects.dspace.org) website @OSUOSL-->
    <server>
       <id>website</id>
       <username>YourOSUOSLUserName</username>
       <privateKey>[Full-path-to]\.ssh\id_rsa</privateKey>
       <passphrase>YourKeyPassphrase (if necessary)</passphrase>
    </server>
  </servers>
</settings>

If you don't yet have a ~/.m2/settings.xml file, you should create one, and copy the full contents above (obviously make sure to put in your username and password).

...

  1. In a separate directory, check out the newly-tagged release from subversion and "mvn install" it.
  2. Now, go back to the directory which has your checkout of 'trunk' (which was used in the above steps)
  3. Run , mvn release:perform
    • If your GPG Code Signing Key isn't found by Maven, you may need to specify your GPG code signing key and passphrase as arguments to the above command: (e.g.) mvn release:perform -Darguments="-Dgpg.keyname=YourKeyId -Dgpg.passphrase=YourKeyPassword"
    • By default, Maven should just prompt you to specify your GPG passphrase

If any errors or problems occur during the deploy, you can re-run mvn release:perform safely after fixing those issues (re-running it will just overwrite existing staged contents).

Verify and Promote Staged Artifacts

...