Linux Development Setup

See Also: MavenInfo, wiki:Developers

Required Software

Optional Software

Basic Build For the Impatient

  svn co http://svn.topazproject.org/svn/head/
  cd head
  mvn

Please see below for more info and if you plan on making any changes...

Subversion Repository Design

The subversion repository is located at http://svn.topazproject.org/svn/ and can be browsed directly; to check out a working copy of the latest working code: 

  svn co http://svn.topazproject.org/svn/head/

The repository (follows the subversion guidelines) comprises of:

  • branches - Various branches to the main working code
  • head - Main working code
  • private - Private tree for developer's (sandbox)
  • tags - Tag marking various releases
  • vendor - External code/resources used by modules

Building

  1. To build everything under head: 
      mvn clean install
    Note: if this is the first time you're building then just run mvn as the clean will fail in this case.
  2. To build the RPMs, you need to be on a redhat/fedora/centos system with rpm development tools installed. First clean out all build directories using the following command: 
    mvn clean
    Check that your source code tree is upto date and contains no surprises: 
    svn stat
    You should not see any files listed. Then rebuild everything with: 
    mvn -Ppackages,rpm
    This will produce rpm files. Use find head/packages -name '*.rpm' to find them.

Profiles

There are currently several maven profiles in use for controlling the build (profiles are enabled with '-P<profile1>,<profile2>,...'):

'packages'
enable this to build the various packages; this is in a profile because building these takes a long time and they are not usually needed during development.
'rpm'
enable this to build the rpm's; requires that the 'packages' profile also be enabled. This is in a separate profile because building rpm's only works on rpm-based linux systems.
'release'
automatically enabled when building a release.
'it'
enable this to run the ambra integration tests.
'reports'
enable this when generating reports (i.e. the running the 'site' or 'site-deploy' goals)

There are additional profiles in various of the plos/libs packages for running various scripts via maven - see the respective poms for details. For example to run RunItql using maven, use: 

mvn -Prunitql exec:java -Dargs="-ef /tmp/example.itql" -f plos/libs/runscripts/pom.xml

Installing and running stuff on your local machine in the specified order

  1. Build and install everything in local repository by running this under head:
    • mvn clean install
  2. To install ESUP CAS Quick Start (ecqs) single signon server:
    • mvn ant-tasks:ecqs-install
  3. To install Mulgara:
    • mvn ant-tasks:mulgara-install
  4. To install Fedora:
    • mvn ant-tasks:fedora-install
  5. To install Search:
    • mvn ant-tasks:search-install
  6. To start the ESUP CAS Quick Start (ecqs) single signon server:
    • mvn ant-tasks:ecqs-start
  7. To start mulgara:
    • mvn ant-tasks:mulgara-start
  8. To start fedora (and mckoi):
    • mvn ant-tasks:fedora-start
  9. To start Search:
    • mvn ant-tasks:search-start
  10. To start ambra
    • mvn jetty:run (in plos/webapp)
  11. To stop Search:
    • mvn ant-tasks:search-stop
  12. To stop fedora (and mckoi):
    • mvn ant-tasks:fedora-stop
  13. To stop mulgara:
    • mvn ant-tasks:mulgara-stop
  14. To stop ecqs:
    • mvn ant-tasks:ecqs-stop

Some build/run related issues

  1. Why don't the ecqs or fedora servers reflect the changes from an 'svn update' even after doing an 'mvn ant-tasks:ecqs-install' or 'mvn ant-tasks:fedora-install'?
    1. It is because, both these ant-tasks pick up the packages to install from your local maven repository (by default). Local maven repository will be updated only when you do a 'mvn install'.
  2. For the ambra project to work with ESUP CAS Quick Start, run 'mvn clean jetty:run' in the plos/webapp directory after ESUP CAS Quick start has been installed and is running. Additionally, SSL has to be setup first on ambra. The certificate for the ambra machine has to be trusted by the CAS server. Since these are self-signed at the moment, you must import it into your local store. By default, ecqs and ambra are running on the same machine. Plosone will use the cert generated by the ecqs install process. You then just need to import that certificate into the local store, e.g. 
    keytool -import -trustcacerts
        -alias jakarta-tomcat -storepass changeit 
        -file ~/topazproject-install/esup-cas-quick-start-2.0.6-1/tmp/cert.pkcs7 
        -keystore $JAVA_HOME/jre/lib/security/cacerts
    Path to cacerts depends if you are using JDK or JRE. It could just be $JAVA_HOME/lib/security/cacerts if you're using the JRE. The default password is changeit, but you may have changed yours at some time in the past. The keytool program is typically in the bin directory of the JDK.
  3. In order for jetty to reload properly (mvn jetty:run) you need create the file src/main/resources/carol.properties in the webapp with the following contents (see also http://docs.codehaus.org/display/JETTY/JOTM ): 
    carol.start.jndi=false
carol.start.rmi=false
carol.jvm.rmi.local.call=true
carol.jndi.java.naming.factory.url.pkgs=org.mortbay.naming
    Otherwise you'll get a javax.naming.InvalidNameException: RegistryContext: can only list "".

SVN Issues

403 Forbidden (http://svn.topazproject.org) while doing a checkin
Because you have not been given commit privileges. Talk to the system administrator.

Attachments