--- Deployment --- Andrés Gómez Casanova --- 2010-06-09 ---

Deployment

Binaries deployment

Preliminary work

  • Describe the release in the changes.xml file (source-code/src/changes) by defining a new release.
  • Modify the pom.xml of the source-code module in order to change all for the new release. Note: look for the RELEASE word.
  • Modify the files ABOUT.txt and LICENSE.txt and put the right version and dates.
  • Tests if everything is okay.
    cd user-site
mvn clean
mvn site:stage
cd ..

cd source-code
mvn clean
mvn package
mvn site
mvn javancss:report
mvn site:stage
cd ..
  • Delete any distribution in the local repository.

    In UNIX-like:

    rm -Rf ~/.m2/repository/name/

    In Windows:

    del "%HOMEDRIVE%%HOMEPATH%"\.m2\repository\name

Build

  • To create the binaries using Maven.
    cd source-code
mvn clean
mvn -P release
cd ..

    The binaries will be in the source-code/main/target directory, and the files are sa-distribution.zip and sa-distribution.tar.gz.

Release

The release is notified in these ways:

Notification

To notify the new release:

Site deployment

  • It is necessary to change some links before the final deployment.
    • In the site.xml and site_es.xml
      <menu name="References" inherit="bottom">
<item name="Developer Site" href="reference/xxxxxx/" />

      Where xxxxxx has to be change to the deployed version.

      cd user-site
mvn site
mvn site:deploy
cd ..
cd source-code
mvn -P release-site site
mvn javancss:report
mvn -P release-site site:deploy
cd ..

      It is necessary to create the ssh shell with Source Forge. For more information, visit configuration page.

Preparing next version.

  • Create a new branch in the SVN repository.
  • Modify the files ABOUT.txt and LICENSE.txt and put the right version and dates.
  • Modify all pom.xml of the source-code module in order to change to the new development version.
  • If the year is different, it is necessary to change the year in the license of all files.