View source

<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 .war

 Yes
cacheRep

Equivalent to the --cacherep command line option. Specifies the folder to use for caching downloaded modules. (default: ~/.ceylon/cache)

 No
config

Equivalent to the --config command line option. Specifies the configuration file to use for this tool. (default: ./.ceylon/config)

 No
cwd

Equivalent to the --cwd command line option. Specifies the current working directory for this tool. (default: the directory where the tool is run from)

 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: true).

 No
inheritAll

Whether a task should inherit environment and properties. Only applies when forked == true.

 No
linkWithCurrentDistribution No
name

Equivalent to the --name command line option. Sets name of the WAR file (default: moduleName-version.war)

 No
noDefaultRepositories

Equivalent to the --no-default-repositories command line option. Indicates that the default repositories should not be used.

 No
offline

Equivalent to the --offline command line option. Enables offline mode that will prevent connections to remote repositories.

 No
out

Equivalent to the --out command line option. Sets the output directory for the WAR file (default: .)

 No
overrides

Equivalent to the --overrides command line option. Specifies the XML file to use to load module overrides. See http://ceylon-lang.org/documentation/current/reference/repository/maven/ for information. Experimental.

 No
resourceRoot

Equivalent to the --resource-root command line option. Sets the special resource directory whose files will end up in the root of the resulting WAR file (default: web-content).

 No
resultProperty

The ant property to set to the Ceylon program exit code

 No
stacktraces

Equivalent to the --stacktraces command line option. If an error propagates to the top level tool, print its stack trace.

 No
sysRep

Equivalent to the --sysrep command line option. Specifies the system repository containing essential modules. (default: $CEYLON_HOME/repo)

 No
verbose

Equivalent to the --verbose command line option. Produce verbose output. If no flags are given then be verbose about everything, otherwise just be verbose about the flags which are present. Allowed flags include: all, loader.

 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 <rep> defined outside this task.

 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 <reposet> defined elsewhere.

 No

See also