This shows you the differences between the selected revision and the current version of the page.
| deployment | deployment 2010/04/07 07:22 current | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | Once a build a satisfying, it can be published using: | ||
| + | mvn deploy -Dmaven.test.skip=true | ||
| + | |||
| + | ===== Deployment of ZIP archives ===== | ||
| + | |||
| + | The 3 archives (sources, binaries and Javadoc) are copied automatically, using SCP, into ///public_html/download/doolin/// | ||
| + | |||
| + | ===== Deployment of Javadoc ===== | ||
| + | |||
| + | The Javadoc ZIP is automatically deployed by running remotely the following script using SSH: | ||
| + | |||
| + | <code shell> | ||
| + | DOOLIN=/home1/doolingu/public_html | ||
| + | DOWNLOAD=$DOOLIN/download/doolin | ||
| + | REPORTS=$DOOLIN/reports | ||
| + | |||
| + | TARGET=apidocs | ||
| + | |||
| + | cp $DOWNLOAD/Doolin-$1-doc.zip $DOWNLOAD/javadoc.zip | ||
| + | mv $DOWNLOAD/javadoc.zip $REPORTS | ||
| + | |||
| + | unzip $REPORTS/javadoc.zip -d $REPORTS/javadoc | ||
| + | |||
| + | rm -rf $REPORTS/$TARGET | ||
| + | mv $REPORTS/javadoc $REPORTS/$TARGET | ||
| + | rm -f $REPORTS/javadoc.zip | ||
| + | </code> | ||
| + | //javadoc.sh// | ||