Monasca common classes
Go to file
Craig Bryant 022d1a5a40 Add missing copyrights
Change-Id: If7720d36d6a229ecf0084c1561a6a4dc9fff16d8
2015-02-17 15:26:07 -07:00
java Add missing copyrights 2015-02-17 15:26:07 -07:00
.gitignore added test for parsing strings 2014-07-09 15:35:52 -07:00
.gitreview Get initial build to work 2014-07-20 08:23:35 -06:00
LICENSE Added license file 2014-05-01 16:22:06 -07:00
pom.xml Change package names from com.hpcloud to monasca.common 2014-10-14 10:02:34 -06:00
README.md Change package names from com.hpcloud to monasca.common 2014-10-14 10:02:34 -06:00
run_maven.sh Changes to use monasca instead of mon 2014-07-23 08:40:26 -06:00

Overview

monasca-common is a collection of sub-projects containing reusable application and platform code for building monitoring related services.

Build Instructions

Download and do mvn install.

cd java
mvn clean install

There is a pom.xml in the base directory but that should only be used for the StackForge build. The issue is that currently StackForge's bare-precise system only has Maven 2 on it and at least one of the modules of monasca-common requires Maven 3.

In order to get around this problem, the pom.xml in the base directory uses the exec-maven-plugin to run the script run_maven.sh. This script checks if the version of mvn is Maven 3 and if it is not, it downloads Maven 3 and then uses it to run the build in the java directory.

In addition, the run_maven.sh script copies the jar files that get built from java/*/target directories to the target directory in the base project directory. This is because the StackForge "monasca-common-localrepo-upload" job uploads any jar files from that directory to http://tarballs.openstack.org/ci/monasca-common. Copying the jar files to that directory made it so there didn't have to be changes made to the "monasca-common-localrepo-upload" job. The build for monasca-thresh downloads the jars it depends on from that location on tarballs.openstack.org.

A change has been submitted to StackForge to switch to bare-trusty for this build in the hopes that those systems will have maven 3, but it is not known how long that change will take to be accepted.

Application Specific Sub-Projects

Platform Sub-Projects