Attribute Name |
Attribute Description |
Required |
version |
Optional string attribute used to specify the version of the build.
If it is specified, the file name of every module produced by this build will contain
given version expression.
|
No |
debug |
Optional boolean attribute used to specify whether this build is a debug build.
Default value is 'false', which means that produced modules will not contain debug information. |
No |
turbobuild |
Optional boolean attribute used to specify whether this build should
aim for a speed (turbobuild='true') or low memory usage (turbobuild='false').
Default value is 'true', which means that the build will attempt to run as fast as posible
which uses more memory. |
No |
compileclasspath |
The optional path to use as additional classpath during compilation.
This may be necessary when inserted handcoded implementation classes have compile time dependencies
on other third party jar files.
|
No |
gendir |
The mandatory directory location where intermediate java source files shall be stored.
Directory will be created if it does not exist. Directory will be cleared of any existing files if it does exists. |
Yes |
classdir |
The mandatory directory location where intermediate java class files shall be stored.
Directory will be created if it does not exist. Directory will be cleared of any existing files if it does exists. |
Yes |
libdir |
The mandatory directory location where produced java archives files shall be stored.
Directory will be created if it does not exist |
Yes |
typessrcdir |
The optional directory location where hand coded data types java source resides.
This directory will be used to search for custom data types source (ie. DataTypes which are not
realised by any of the TypeTemplates. |
No |
implssrcdir |
The optional directory location where hand coded service implementation java source
resides. This directory will be used to search for business services custom source. |
No |
srcdir |
The optional directory location where hand coded java source resides.
This directory will be used to search for custom data types and custome service implementations.
Note that if sources for data types and implementations reside in different directories, attributes
'typessrcdir' and 'implssrcdir' should be used. |
No |
Subelements of this task are definitions of the build results. Following subelements are supported: