ContentMine/cm-pom

Name: cm-pom

Owner: The ContentMine

Description: Parent POM for ContentMine Java/MVN stack

Created: 2017-02-02 16:34:11.0

Updated: 2018-04-06 16:19:13.0

Pushed: 2018-04-06 16:20:33.0

Homepage:

Size: 5358

Language: Shell

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

cm-pom

Parent POM for ContentMine Java/MVN stack

ami-stack 2017-03

NOTE do not use the scripts till I have checked the branches

Currently the major effort is in ami. The build process requires 11 builds and is best done from a script.

The stack is

om
id


eanalysis
svg
xml
ject
ramanalyzer
a

The dependencies may change but the order will be defined in the build.sh file.

Before building you should clone all these from github. Once installed status.sh should update before building. So:

itial
clone https://github.com/contentmine/cm-pom.git
clone https://github.com/contentmine/euclid.git

clone https://github.com/contentmine/ami.git

for subsequent builds

ce status.sh

status.sh

This script checks that there are no uncomitted components or unpushed ones. Mainly used by PMR. It will issue commands of the form:

orkspace/cmdev

m-pom
 "======= CM-POM ==="
pull
status
push
.

uclid
 "======= EUCLID ========"
pull
status
push
.

vg
 "======= SVG ========"
pull
status
push
.

and all the way to AMI.

It does NOT commit or merge. AFAIK pull and push are idempotent and so can't do any harm.

To run

ce status.sh

build.sh

This should be used for all builds. It starts:

in/bash


orkspace/cmdev

m-pom
clean install
.

uclid
clean install
.

and goes through to ami.

run by

ce build.sh

The output may be large for some modules. You may wish to

ce build.sh > build.log