Build a release

with Maven's [release plugin]:

  • note: these steps were used to release Pustefix 0.14.7, using Maven 2.2.1 and Release Plugin 2.0 beta 9

  • optional: save sites pustefix@pustefixhp.schlund.de/var/www/pustefix-docs/trunk to a release directory
  • set the username in your .m2/settings.xml (you cannot deploy to the pustefix repository without this): 
      <servers>
    <server>
      <id>pustefix</id>
      <username>pustefix</username>
    </server>
  </servers>
  • Trac roadmap: mark the current milestone an finished and move all tickets to the next milestone.
  • make sure that all modules have the correct version: mvn clean && grep -r 0\\.14\\. . | grep -v \\.svn | grep -v 0\.14\.8-SNAPSHOT (where 0.14.8-SNAPSHOT is the current version).
  • make sure your workspace if committed
  • run svn up to work-around an release:prepare problem
  • mvn -B release:prepare
    • if it fails because an to-be-released artifact is not found: run mvn install and try again
    • note: 2.0. release plugin failed very early in this step with a null version exception for xml-resolver:xml-resolver
  • mvn release:perform
    • also building the site failed persistently with ClassNotFoundException for GlobalConfig (yes, I tried mvn install, it did not helped).
  • cd target/checkout
    • deploy to corporate repository: mvn clean deploy -Poneandone
    • deploy the documentation: mvn site-deploy
  • login to pustefix@… and adjust the version number in repository/maven/archetype-catalog.xml

Configure Editor for your Application

  • add a dependency to the Editor war in order to force a download into the local repository
  • add a dependency to the Editor backend to your application
  • adjust the elements in /project/editor in your project.xml to point to the editor; specify a secret.
  • in the editor, adjust WEB-INF/editor-locations.xml to point to your editor, with the secret specified in the step before.