Cúram Build Settings

A number of parameters may be passed when performing the build. They should be passed in the following way build server -Dsome.setting=somevalue. These parameters are:

Table 1. Build Configuration Settings
Parameter	Values	Description
dir.sde	directory name	The name of the directory containing the installed SDEJ that you want to use for this build. The default is the directory referred to by the CURAMSDEJ environment variable.
prp.loglevel	info warn error verbose debug	The logging level used when recording build progress to the build log. The default is info.
prop.file.location	directory name	Override the location of the directory that is used to pick up the property files. By default the <ProjectName>/properties directory is used.
prp.maxcodetablecodelength	number	Override the maximum length of a code table `code`. This is used for validation of codetables during generation, where it is desired to ensure that the code length defined in the codetables being generated do not exceed the length specified. This is to ensure, you catch errors before entering codetables onto the database. This does not override the maximum length on the database Cúram Build Settings.
prp.maxcodetablenamelength	number	Override the maximum length of a code table `name`. This is used for validation of codetables during generation, where it is desired to ensure that the name length defined in the codetables being generated do not exceed the length specified. This is to ensure, you catch errors before entering codetables onto the database. This does not override the maximum length on the database Cúram Build Settings.
prp.maxcodetabledescriptionlength	number	Override the maximum length of a code table `description`. This is used for validation of codetables during generation, where it is desired to ensure that the description length defined in the codetables being generated do not exceed the length specified. This is to ensure, you catch errors before entering codetables onto the database. This does not override the maximum length on the database Cúram Build Settings.
prp.warningstoerrors	true false	Indicates that warnings thrown when extracting and generating from the model, code table and message files should be treated as errors (an error typically terminates the process). The default is `false`.
prp.forcegen	"-force:modelgen"	Indicates that the build should progress even if errors are found when generating code from the model. The default is that this should not occur. This means that if this flag is set and errors are found during generation, the build is not interrupted after the modelgen build target is executed. Once this target is complete it will eventually pass onto the compile.generated target. See What is happening under the hood for more details. Note: The errors are still reported.
prp.noninternedstrings	true false	Indicates whether code table artefacts should be generated with strings which will not be interned. This is described in more detail in ctgen. The default is `true`.
curam.using.dbcs	true false	Should be set if the Cúram model contains DBCS (Double Byte Character Set) characters. If defined the Cúram application model is first processed by the utility native2ascii. The Model Extractor then uses this new reworked model to produce <project>.xml file. If this property is not specified the Model Extractor takes original model file as its input.
curam.using.nonascii	true false	Should be set if the Cúram model contains non ascii characters. If defined the application model is first processed by the utility native2ascii. The Model Extractor then uses this new reworked model to produce <project>.xml file. If this property is not specified the Model Extractor takes original model file as its input.
extra.generator.options	String	Specifies additional command line parameters for the server code generator. These settings are described in Generator Settings.
portability.warnings	BUILD, DMX	Specifies whether the SQL Checker should determine if the build is portable to other database platforms and whether the Data Manager files are valid. The default is to check all of these.
enablefacade	true false	Specifies that the build should generate the session beans and their corresponding deployment artefacts for model elements identified as facades. The default is `false` which means they will not be generated.
prp.genschemavalidation	true false	Indicates that the.xml file produced by the model extractor will be validated against a schema when it is being parsed and used by the code generator to generate the application code. The default is `false`.

Database update for code table property changes: The relevant database column lengths must be altered to support the changes made by using the prp.maxcodetablecodelength, prp.maxcodetablenamelength, or prp.maxcodetabledescriptionlength properties.

The columns should be altered using the Data Manager. In each case a handcrafted SQL script that alters the relevant column's length should be added to the custom database scripts folder. This script should then be added as an entry to the datamanager_config.xml file before loading the code tables into the database. Please refer to Data Manager for further information on using the Data Manager.