If you release from command line it's recommended to close eclipse, disable eclipse' autobuild (Project -> Build Automatically) or close the project in eclipse. Otherwise eclipse might clear the project target folder while maven is using the compiled resources and will fail at this point.
Run command (please update the versions given in this example to the one of your project)
If you are doing a hotfix release where the major version does not change (leftmost number) you can just run:
mvn release:prepare release:perform
Recover from errors
To recover the project after a failed release attempt you have to call mvn release:rollback release:clean. This will also remove the temporary file release.properties that you might see in this situation.
Rollout of Services and Applications:
The general workflow is (also explained before on this page):
CLEAN -> COMPILE -> VERIFY -> INSTALL -> DEPLOY/RELEASE-> ROLLOUT
In Git there is a repository containing the rollout script: https://git.acc.gsi.de/fcc-applications/common-scripts/
This script (rollout) should be installed in the group directory (/common/usr/cscoap/bin) on all environments (development, integration and production).
If the script is installed rolling out an artifact is easy. The only precondition is, that the artifact was built using the 'csco-parent-java-bundle' as a parent. This will create a ZIP file with all dependencies for this product during the deploy phase, and this ZIP file is used for the ROLLOUT.
The syntax for the rollout script is as follows:
$ rollout -h usage: rollout [-h] [--repo REPO] [--dest DEST_DIR] [--yes] [--not-current] g:a:v Rollout Script - This script is used to download artifacts from the central repository. The contents will be extracted to a directory on disk were the user expects the files to be located. positional arguments: g:a:v group, artifact and version to rollout e.g. de.gsi.cs.co.ap:feedback:0.0.2 optional arguments: -h, --help show this help message and exit --repo REPO the repository to use e.g. csco, csco-snapshot. Defaults to "csco" --dest DEST_DIR The directory were the files are extracted to. Defaults to "/common/usr/cscoap/htdocs/applications" --yes If specified all questions are answered with "yes" --not-current If specified the "current" symlink is not updated.
Make sure you're logged on to the environment you want to perform the rollout to (asl3xx for production, vmla006 for integration and asl7xx for development)!
A usage example for an application 'parammodi-app' would look like this:
To start a service you have to provide the environment to starting it against. At the moment there are the options --dev, --int and --pro. If you want to start a service in the production environment it would look like this: