Note: information on this page refers to Ceylon 1.2, not to the current release.
<ceylon-war>
Ant task
Usage
Note: You must declare the tasks with a <typedef>
.
Description
Generates a WAR file from a compiled .car
file
The <ceylon-war>
ant task wraps the ceylon war
command.
Attributes
Attribute | Description | Required |
---|---|---|
module |
The module for which to create the |
Yes |
cacheRep |
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 |
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 |
name |
Equivalent to the |
No |
noDefaultRepositories |
Equivalent to the |
No |
offline |
Equivalent to the |
No |
out |
Equivalent to the |
No |
overrides |
Equivalent to the |
No |
resourceRoot |
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 |
verbose |
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 |
<exclude>
Equivalent to the --exclude-module
command line option.
Excludes modules from the WAR file. Can be a module name or a file containing module names. Can be specified multiple times. Note that this excludes the module from the WAR file, but if your modules require that module to be present at runtime it will still be required and may cause your application to fail to start if it is not provided at runtime.
Element | Description | Required |
---|---|---|
module |
The module to exclude |
Yes |
<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 |