Skip to content
golbi edited this page Oct 15, 2013 · 6 revisions

Maven

Typically CANL is build using Maven without any magic: mvn compile & test & install work as usual.

Deploying is configured to push artefacts to Maven Central repository via Sonatype infrastructure.

OS-specific packages

It is possible to build RPMs and deb files with CANL library included. So far this was tested against:

  • RPM: SL5, SL6, several recent Fedora versions, Centos 5 Centos 6
  • deb: Debian 6 Other distros as SUSE will require minor modifications of building logic. Note that there are 2/3 dependencies of the library: BouncyCastle and Apache Commons IO. Commons-IO in version 1.4 is available in all tested distributions. BC is sometimes problematic - CANL 1.x requires version 1.46, CANL 2.x requires version 1.48. Currently SL5/Centos5 doesn't include BC 1.46 and it was repackaged in the EMI repository. SL6/Centos6 does contain 1.46 so no problem with CANL 1.x there. CANL 2.x was not yet released but BC dependency troubles are foreseen :-)

To build RPM/deb you must run the command on an appropriate OS. So assuming you are on Centos 6 you will build packages for Centos 6, which will work for compatible SL6 but not for SL5 or Centos 5 (old RPM version).

Command: mvn package -Ppackman -Dpackage.release=1 -DindexJars=true

Use a proper package release number.

More switches and advanced options (including info on porting to new distributions): Packman

Clone this wiki locally