<ceylon-test>
Ant task
Usage
Note: You must declare the tasks with a <typedef>
.
Description
Executes tests
The <ceylon-test>
ant task wraps the ceylon test
command.
Attributes
Attribute | Description | Required |
---|---|---|
autoExportMavenDependencies |
Equivalent to the |
No |
cacheRep |
Equivalent to the |
No |
compile |
Equivalent to the |
No |
config |
Equivalent to the |
No |
cwd |
Equivalent to the |
No |
errorProperty |
The ant property to set to true in the event of an error |
No |
executable |
The location of the ceylon executable script. |
No |
failOnError |
Whether an error in executing this task should fail the ant build |
No |
flatClasspath |
Equivalent to the |
No |
fork |
Whether the task should be run in a separate VM (default: |
No |
inheritAll |
Whether a task should inherit environment and properties. Only applies when |
No |
linkWithCurrentDistribution |
Equivalent to the |
No |
noDefaultRepositories |
Equivalent to the |
No |
offline |
Equivalent to the |
No |
overrides |
Equivalent to the |
No |
report |
Equivalent to the |
No |
resultProperty |
The ant property to set to the Ceylon program exit code |
No |
stacktraces |
Equivalent to the |
No |
sysRep |
Equivalent to the |
No |
tap |
Equivalent to the |
No |
verbose |
Equivalent to the |
No |
version |
Equivalent to the |
No |
Nested elements
<define>
A <define>
element is used to set system properties for the ant task being executed.
Equivalent to the --define
command line option.
Set a system property
The value for the system property can either be passed as a value
attribute:
<define key="org.example.helloworld.greeting" value="Hi"/>
or it can be the text between the begin and end tags:
<define key="org.example.helloworld.greeting">Hi</define>
Alternatively, it is posible to dispense with the attributes and use the syntax
<define>org.example.helloworld.greeting=Hi</define>
Element | Description | Required |
---|---|---|
key |
The property to be defined |
No |
value |
The value of the define |
No |
<module>
A module to test
A <module>
element must specify a name, and may specify a version. If the relevant ceylon task don't require a version it will be ignored.
Element | Description | Required |
---|---|---|
name |
The module name. |
Yes |
version |
The module version. Whether this is required depends on the task |
No |
<moduleSet>
Modules to test
A <moduleset>
containing a number of <sourcemodule>
s and/or <module>
subelements. It can be defined at the top level and then used by reference using the refid
attribute, so you don't have to repeat the same list of modules all the time.
Element | Description | Required |
---|---|---|
refid |
A reference to a |
No |
<rep>
A module repository containing dependencies. Can be specified multiple times. Defaults to <rep url="./modules"/>
.
Element | Description | Required |
---|---|---|
url |
The URL or path of the module repository. |
Yes, unless a `refid` is given |
refid |
A reference to a |
No |
<reposet>
A set of module repositories containing dependencies. Can be specified multiple times. Default to modules
.
A <reposet>
element contains a number of <repo>
and/or <reposet>
elements. It can be defined at the top level, and then used by reference using the refid
attribute so you don't have to repeat the same list of repositories all the time.
Element | Description | Required |
---|---|---|
refid |
A reference to a |
No |
<sourceModules>
Modules to test
Includes all the ceylon modules in a given source directory, as specified by the dir
attribute. This saves you having to explicitly list all the modules to be compiled, you can instead just compile all the modules in a given directory.
Element | Description | Required |
---|---|---|
dir |
The directory containing module source files |
No |
<test>
The name of a test to run. If no <test>
s are given then all tests in the given <module>
/<moduleset>
/<sourcemodule>
Equivalent to the --test
command line option.
Specifies which tests will be run.
Element | Description | Required |
---|---|---|
test |
A test to run. |
No |