Versions Compared

Old Version 98

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 99

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Adding some more details based on recent findings with 3.0-rc releases

...

Info
If you need to re-run the Dry Run
If you need to re-run the Dry Run

If you notice an issue or an error occurs, you can re-run the Dry Run using the following command:

  • mvn release:prepare -DdryRun=true -Dresume=false

You can also clean up any of the release files that the Dry Run created, and just re-run it.

  • mvn release:clean
  • mvn release:prepare -DdryRun=true

Tag and Increment Version

...

You will also have to enter in your GPG passphrase (which you established when you created your Code Signing Key).

Assuming everything worked, you should see something like below. (Don't worry about the "SKIPPED" messages, those are normal, as the actual release process just runs from the "Parent Project")

Code Block
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] DSpace Parent Project ............................. SUCCESS [2.320s]
[INFO] DSpace Services Framework :: API and Implementation  SKIPPED
[INFO] DSpace Kernel :: API and Implementation ........... SKIPPED
[INFO] DSpace Addon Modules .............................. SKIPPED
[INFO] DSpace Kernel :: Additions and Local Customizations  SKIPPED
[INFO] DSpace XML-UI (Manakin) ........................... SKIPPED
[INFO] DSpace XML-UI (Manakin) :: Local Customizations ... SKIPPED
[INFO] DSpace LNI ........................................ SKIPPED
[INFO] DSpace LNI :: Local Customizations ................ SKIPPED
[INFO] DSpace JSP-UI ..................................... SKIPPED
[INFO] DSpace JSP-UI :: Local Customizations ............. SKIPPED
[INFO] DSpace SWORD ...................................... SKIPPED
[INFO] DSpace SWORD :: Local Customizations .............. SKIPPED
[INFO] DSpace SWORD v2 ................................... SKIPPED
[INFO] DSpace SWORD v2 :: Local Customizations ........... SKIPPED
[INFO] DSpace SOLR :: Local Customizations ............... SKIPPED
[INFO] DSpace OAI 2.0 .................................... SKIPPED
[INFO] DSpace OAI 2.0 :: Local Customizations ............ SKIPPED
[INFO] DSpace Assembly and Configuration ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
Note
title
Info
titleIf you receive a project dependency error while using Maven 2

The mvn release:prepare command may fail to compile part way through the process, complaining that an internal project dependency is not met. This seems to only occur using Maven 2. If this occurs, don't worry. Just . You just may need to ensure those dependencies get installed to your local cache.  To fix this, you should be able to run the following:

  1. mvn release:clean   (clean out any files created by the previous "mvn release:prepare")
  2. mvn install
  3. mvn release:prepare
Note
titleBacking out of changes

If backing out of this step is needed for any reason, the following will restore the github repository and your working copy to the state it was previously in:

  1. mvn release:rollback
    • Warning: running a "mvn release:rollback" will perform an immediate, automatic push to GitHub master, rolling back any previously committed POM version changes.
    • If you want to avoid the immediate, automatic push to GitHub master, you may be able to use "mvn release:clean" to just clean up the locally made release preparations.
  2. Now delete the tag in GitHub (local & remote)
    • git tag -d dspace-x.y
    • git push origin :refs/tags/dspace-x.y

...