Peregrine Development

From BioAssist
Revision as of 16:49, 24 March 2010 by Dmitry Katsubo (Talk | contribs)

Jump to: navigation, search

Peregrine for Developers

This article targets Java developers, who would like to contribute into Peregrine development.

You have to follow the following procedure:

  • Register at NBIC gForge and submit registration information to Peregrine administrators (e.g. to Dmitry Katsubo or Bharat Singh).
  • In a while you will be granted an access to SVN. In Eclipse you should checkout the project using URL or using CLI:
    svn checkout --username yourdevelopername
    (you will be asked for password and permission to save server certificates locally)
  • Now setup Maven[1]:
    • Download and install Maven+JDK as described here.
    • Tune system variables. You need to create JAVA_HOME and M2_HOME variables and append the path to maven's bin directory to your PATH, as shown on this screenshot.
  • Go to your data-mining project and execute
    mvn eclipse:eclipse
    to download all necessary artefacts[2]. Remove .project files for POM-type projects (namely: data-mining\.project, data-mining\ontology\.project, data-mining\peregrine\.project) - this will allow Eclipse to see correctly the list of subprojects when scanning for new projects during import step.
  • Define a classpath variable M2_REPO in Eclipse, which should point to your local maven repository (C:\Users\me\.m2\repository).
  • Switch your Eclipse to "Working Sets" top-level elements (as shown here) and create new working set Peregrine.
  • Go to File -> Import and select General -> Existing projects into workspace as shown here, press Next and import all projects into Peregrine workspace.
  • Now head project can be closed unless you wish to use some information from it.

Switching SVN credentials

It might happen, that you would like to change authentication information for SVN access. Subclipse running over SVNKit stores authentication information in configuration\org.eclipse.core.runtime\.keyring (see here and here for more information).


  1. You don't need to setup maven plugin for Eclipse. If you do so, this plugin will handle M2_REPO variable
  2. Sometimes in Linux (Ubuntu), you may receive errors due to problems in maven dependencies and permission setting.
    • solution #1 is to run "sudo mvn eclipse:eclipse"
    • solution #2 (seems better) is to remove the M2_HOME system variable