Developers/Phing

Introduction
Currently we use phing as build system. Calling phing from any directory within the Arcavias source code directory you can install Arcavias, run the unit tests or build the translation files for example.

Options for phing
In order to find out what targets are defined for phing take a look at the build.xml in the Arcavias root directory (there are more build files distributed over many directories referenced in the master build file).

Some targets might depend on others. The most important targets for you as an administrator are "setup" to install Arcavias and "test" to find out, if Arcavias is still working as it should:

phing setup phing test

If you would like to test Arcavias on your hardware you can use target "setupperf" to write performance test data to the database and browse the shop site "Perfomance" in the front end using the Zend Framework demo application in dev/zfapp. You might have to activate the performance site in the Arcavias administration interface.

These targets are available:


 * all : executes all defined targets
 * setup : Sets up the database and writes the unit test data to the database
 * setupperf : Sets up the database and writes the perfomance test data to the database
 * coverage : Generates a code coverage report
 * coverageext : Generates a code coverage report for specific extension directory given via "-Ddir=ext/ "
 * test : Executes the unit tests
 * testext : Executes the unit tests for specific extension directory given via "-Ddir=ext/ "
 * testperf : Executes the performance tests
 * check : Executes the code sniffer
 * checkext : Executes the code sniffer for specific extension directory given via "-Ddir=ext/ "
 * doc : Generates the API documentation from the PHPDoc blocks
 * clean : Cleans up temporary files
 * i18n : Creates all translation files
 * build : Generates all files to be generated
 * deploy : Executes all deployments