Versions Compared

Old Version 215

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 216

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

Info
titleIf you need to re-deploy

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


Warning

As of 2022, Sonatype REQUIRES usage of Java 8 (or above) to deploy artifacts into staging. Attempting to use Java 7 will result in "connection reset" errors.  So, when releasing DSpace 5.x (or lower), you must switch to using Java 8 for this step.


Note

If you run into issues, or need to perform the mvn release:perform from a different machine, it is possible to run it simply against the created tag in GitHub.

  1. Create a "dummy" [src]/release.properties file in your local DSpace source directory. It should simply state the basic SCM info for the tag you wish to release, e.g.

    Code Block
    # Location of DSpace's SCM. Keep this as-is.
scm.url=scm\:git\:git@github.com\:DSpace/DSpace.git
# Change this value to point at the tag in GitHub
# For example, this example tells "release:perform" to perform a release to Sonatype based on the 'dspace-6.0-rc1' tag.
scm.tag=dspace-6.0-rc1


  2. Run the specified mvn release:perform command (see above).  Maven will then proceed to checkout the specified tag into your [src]/target/checkout folder, package up the release and send it off to Sonatype.

...