ant build This target compiles all sources, creates java archives, and copies scripts and configurations into the build directory: ${build} The build directory is treated as a live distro which this target will incrementally update. Developers can put the build/bin directory into their path in order to run any scripts or code directly out of the live build: ${build.bin} ant test [ -Dtest=<pattern> ] [-Dprofile=<profile>] [ report ] Execute unit tests and place the output in the build results directory: ${build.results} All test output will be redirected to a file of the form: TEST-<class>.txt The same output is available using an xml file format: TEST-<class>.xml The test system property may be used to restrict the number of tests run by a given invocation of the ant test target. The following command will run just the MongooseTest test case: ant test -Dtest=MongooseTest In addition, patterns may be used to specify more than one test. The following command will run both the MongooseTest and GooseTest test cases: ant test -Dtest=*ooseTest If no test property is specified, the "ant test" target will default to running all available tests for the project or module depending on the current working directory. Test Reports It can be useful to append the report target in order to generate an html summary of the tests that were just run. The following command will run both the MongooseTest and GooseTest test cases and generate an html summary of the results: ant test -Dtest=*ooseTest report See the documentation for the "ant report" target for more details on the generated report. Test Profiles There are a number of profiles defined for running the test suite. These test profiles define how the test should be run. If the test profile is not specified then 'default.testprofile' is utilised. This runs the system tests against the Java InVM broker. Additional test profiles exists as follows: cpp : Runs against the built cpp tree broker. ant report The report target will generate an html summary of the current test results into the report directory: ${build.report} The report target will operate on all results currently in the build results directory. Results are not cleared unless the clean target is used. This means that several consecutive test runs can be summarized into a single report. The following commands will produce a report summarizing both the MongooseTest and GooseTest test cases: ant test -Dtest=MongooseTest ... ant test -Dtest=GooseTest ... ant report ant release The release target generates binary distribution archives and places them into the release directory: ${release} ant release-bin The release-bin target generates binary distribution archives for modules that have a specific binary package configured. To enable for other modules create a target "release-bin" that depends on target "release-bin-tasks". The output is placed in: ${module.release} ant clean The clean target removes build artifacts. When invoked from the project root this target will remove the entire project build and release directories: ${build} and ${release} and ${module.release} When invoked from a specific module, the clean target will delete that modules build root from underneath the project build root: ${build}/<module> ant clean-results The clean-results target removes all test output from the test results directory: ${build.results} ant eclipse Generates project and classpath files for the Eclispe IDE. Requires that the Ant Eclipse task (http://ant-eclipse.sourceforge.net/) has been installed in $ANT_HOME/lib. The following system properties will be passed to the task. These can be usefully overridden from the command line. eclipse.updatealways - forces Eclipse files to be regenerated even if they are newer then the build.xml (default ${eclipse.updatealways}). eclipse.container - controls the Eclipse container (default ${eclipse.container}). eclipse.compilercompliance" - controls the Eclipse compiler compliance (default ${eclipse.compilercompliance}).