Skip to content

Developer's corner

Jump to bottom Edit New page
Robert Munteanu edited this page Jul 12, 2014 · 10 revisions

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
  • 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;
  • 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.
  • Update Eclipse Marketplace listing
  • 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;

Installing the code signing certificate

At one time the first option was successful, but now the second one works. I'm keeping both , for reference.

Binary certificate

  • download the binary certificate from Certum
  • install the certificate : keytool -trustcacerts -importcert -file $CERTIFICATE -alias mylyn-mantis -keystore keystore.jks

Firefox install

Note: the instructions assume the default keystore at ~/.keystore . To use a different keystore pass the -keystore argument to all commands.

  • install the certificate from Certum straight into Firefox
  • 'Export all' the certificate and remember your password
  • Import the Certum CA certificate from http://www.certum.pl/keys/ca.crt using keytool -importcert -file CA.cer -alias certum_ca
  • Import the Certum code signing certificate from http://www.certum.pl/certum/cert,certyfikaty_zaswiadczenia_klucze.xml#codeCa using keytool -importcert -file csca.cer -alias csca
  • Import the certificate into a new keystore using keytool -importkeystore -srckeystore $SRC_KEYSTORE_FILE -srcstoretype PKCS12 -deststoretype JKS
  • (Optional) Rename the certificate using keytool -changealias -alias $OLD_NAME -destalias mylyn-mantis

To validate the installation use the following commands

mkdir test
cd test
jar cf test.jar .
jarsigner test.jar $KEY_ALIAS
jarsigner -verify test.jar

The output should simply be 'jar verified.'.

Add a custom footer
Add a custom sidebar

Clone this wiki locally