Build from Source

Dependencies

• rpm-build
• git
• maven (3+)
• java (1.7)

sudo yum install rpm-build git maven java-1.7.0-openjdk-devel

Setup Environment

There is a possibility of a man-in-the-middle attack when getting artifacts from Maven Central with default settings. The root directory of each maven project has a settings.xml file that will override the default. It is recommended that this setup is used. There are a few options for using the override:

• Copy ./etc/settings.xml to your ~/.m2 directory.
• Specify the file with each build using option -s ./etc/settings.xml.
• Configure this yourself.
• Do nothing, use defaults (NOT RECOMMENDED!).

Checkout and Build

You can build lightblue without any particular options set. It will create all the java artifacts but not package them for deployment (unless you want to just grab the WAR). To get and build all main repos:

for REPO in "lightblue-core" "lightblue-mongo" "lightblue-rest" "lightblue-applications";
do
    git clone https://github.com/lightblue-platform/${REPO}.git
    pushd ${REPO}
    mvn clean install -s ./etc/settings.xml
    popd
done;

There are two profiles that are optional at this time:

• rpm - builds all the RPMs for REST services
• wildfly - change RPM packaging from jbossas (default) to wildfly

Build RPM's for JBoss EAP

The default build of RPM's is for JBoss EAP, so simply include the rpm profile.

To get all dependencies built locally instead of pulled from sonatype follow Checkout and Build steps above.

cd lightblue-rest
mvn clean install -P rpm -s ./etc/settings.xml

Build RPM's for Wildfly

Builds lightblue RPMs for deployment on wildfly. The only difference is where the artifacts get deployed on the filesystem. By default lightblue builds for deployment on JBoss EAP6.

To get all dependencies built locally instead of pulled from sonatype follow Checkout and Build steps above.

cd lightblue-rest
mvn clean install -P wildfly -P rpm -s ./etc/settings.xml