We develop, build and test on a regular basis on MacOS and variants of RedHat/CentOS/Amazon Linux.
We recommend setting the JAVA_HOME environment variable
Mercurial (any somewhat recent version)
You will need to configure to utilize SSL. Please consult Tomcat SSL documentation for more info on this.
Also, make the following modification to your catalina.properties under $TOMCAT_HOME/conf to extend the classpath for each server component WAR file
Set TOMCAT_HOME in your environment if you would like to use Maven to deploy locally.
We expect that more recent versions of Mongo will work, but have not tested them.
Amazon AWS S3
The default main file object repository is S3. You need to create or reuse a an S3 bucket and configure for CORS support as described at the end of this document
Google Drive (optional)
GenomeSpace client applications
These are not part of GenomeSpace per se, but GenomeSpace is meant to enable applications to interact in the cloud.
You will need to install and configure each application that you want to have communicate with your GenomeSpace setup.
A list of the applications currently Gs-Enabled can be found here:
GenomeSpace Tools and Data Sources
To build all GenomeSpace components:
Create a master properties file.
If not specified in the build command line, our Maven build will look for it under:
You will also need in the same directory. It will contain your AWS credentials:
And to configure the Java GS client while executing the tests:
You will find an annotated templates for this file in this repository under the config directory.
The checked in code base for GenomeSpace is currently hard-coded to do cache replication via JMS in a clustered environment.
This might not be what you want to do. If this is the case you will need to edit the following files:
And remove the strings that match the following two regex expressions:
Maven command to build
mvn clean install -Denv-properties-file=MASTERPROPERTIESFILE -Dorg.genomespace.env=URLPROPERTIESFILE
Optional/useful command line options:
Will copy the GenomeSpace server components, the configuration files, and converters to $TOMCAT_HOME. Note that some tests, such as those that include the Client Development Kit depend on GS being initially deployed.
Standard Maven flag to skip tests
Will run all tests/continue build even if some tests fail. It is likely you will need this flag if you run tests as we still have in our code base tests that are hardcoded with our testing infrastructure setup.
Will skip tests related to Dropbox
Will skip tests related to Google Drive
If you have problems or questions you can reach us at:
or post a message to the Genomespace User Forum