Developer's corner

Various development-related pieces of information

Regenerating the Axis Stubs

When a new methods are added to the MantisBT SOAP API or when other compatible changes are made the Axis stubs must be regenerated to take advantage of those changes. The steps which must be performed are:

• Update the mantisbt.soap.version property in com.itsolut.mantis.core/pom.xml to the desired version
• Execute mvn -Prefresh-soap-stubs -pl com.itsolut.mantis.core dependency:copy
• Commit the changes

Code analysis

The project is analysed by Sonar and the results are available publicly at http://nemo.sonarsource.org/dashboard/index/360960 .

Releasing

You should reserve at least one hour for the below operations.

In the below document, $VERSION refers to the simple version, that is X.Y.Z , not the OSGI one, X.Y.Z.qualifier.

• Build release notes
  • Update the com.itsolut.mantis-feature/src/changes/changes.xml file for the latest release
  • Commit and push the changes
• Build update site jars
  • The jars should be signed: mvn clean package -Djarsigner.alias=... -Djarsigner.storepass=... -Djarsigner.keypass=....
    • For now, the jars should be signed using Java 6 only ; See https://bugs.eclipse.org/bugs/show_bug.cgi?id=380779 and http://jira.codehaus.org/browse/MJARSIGNER-21 for more details.
  • If you need code signing certificates, https://www.certum.eu/certum/cert,offer_java_code_signing.xml offers free code signing certificates for Open Source developers. See Setting_up_code_signing for technical details.
  • The release notes are saved in multiple formats in com.itsolut.mantis-feature/target/release-notes
• Tag projects in git;
  • The tag format should be mylyn-mantis-$VERSION
• Upload update site jars to the main update site;
  • a lftp script is found in com.itsolut.mantis-site/upload-to-main-site.lftp. It hardcodes the username, but you can adjust it.
• Upload com.itsolut.mantis-site/target/site_assembly.zip on sf.net;
  • The file name should be mylyn-mantis-$VERSION.zip
  • Update the text release notes as README.
  • Set the newly archived update site as the default download for all platforms.
• announce release on forums;
  • Remove sticky from previous release announcement;
  • Should be a sticky post in the users forum;
• announce release on sf.net;
• update wiki front page;
  • Move the previous version to the Release history page;
  • Put the current version version in place of the previous one;
  • Update requirements if needed;
• Mark the version in Mantis issue tracker as released;
  • If the release date is incorrect, set it to today.
  • Close all tasks resolved in this version.
• Post on freshmeat.net ( rombert );
• Post on dzone.com , for noteworthy changes,( blog post ideally );
• Tweet with dzone or blog link, include #mylyn #mantisbt ;
• Increment version locally using ./set-version.sh X.Y.Z-SNASPHOT;
• Commit and push incremented version to git;