Versions Compared

Key

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

...

This document contains notes and steps required to publish a new release of the Scheduling Assistant source.

Before you begin, read Using Maven for your Jasig project. You'll need a GPG key and authorization to publish to sonatype.

...

  1. Start with a clean checkout of the desired branch that has none of the files in svn:ignore (e.g. scheduling-assistant.properties, integration.properties).
  2. Make sure license and notice files are up to date with mvn license:format and mvn notice:generate. Run svn status -u afterwards to see if any changes need to be committed.
  3. Execute mvn release:prepare -DautoVersionSubmodules=true. The argument will only require you to enter 1 version number to be applied to all the sub modules.
  4. Upon completion you should see the following:
    No Format
    [INFO] Release preparation complete.
    [INFO] ------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO] 
    [INFO] Scheduling Assistant Parent ....................... SUCCESS [3:57.573s]
    [INFO] Scheduling Assistant API .......................... SKIPPED
    [INFO] Scheduling Assistant Mocks ........................ SKIPPED
    [INFO] Scheduling Assistant SPI: Common .................. SKIPPED
    [INFO] Scheduling Assistant SPI: CalDAV .................. SKIPPED
    [INFO] Scheduling Assistant SPI: Relationship Providers .. SKIPPED
    [INFO] Scheduling Assistant WAR .......................... SKIPPED
    [INFO] Scheduling Assistant Portlet ...................... SKIPPED
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESS
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 3:58.945s
    [INFO] Finished at: Wed Sep 21 12:21:52 CDT 2011
    [INFO] Final Memory: 8M/103M
    [INFO] ------------------------------------------------------------------------
    
  5. Execute mvn release:perform. This will upload the artifacts to the sonatype staging repository.
  6. Log into sonatype at https://oss.sonatype.org/
  7. Navigate to Staging Repositories
  8. Select the project in the right frame and hit Close. No Description is required.
  9. Select the same project and hit Release.

In a few hours the new artifact will show up in Maven Central.