grass

grass config

The utility uses a mandatory application level grass config file and one or more optional module level grass config files to generate application config files for different target environments. The module grass config files are optional. They are useful when there are large number of config files and when it becomes difficult to manage using one grass config file for the entire application. If the application uses install tokens, then they are replaced using the token values defined in .grass file in the user home directory.

Details of grass config files

Attribute	Description
grass-app-cfg.gac	The mandatory application grass config file
grass-module1-cfg.gmc	The optional one or more module grass config file

grass-app-cfg.gac

The application grass config file is called grass-app-cfg.gac. This grass config defines various grass sett
A sample grass-app-cfg.gac is shown below,

<?xml version="1.0" encoding="UTF-8"?>

<grass-cfg>
<settings project="Test">
<project-dir>/home/aravsa/dev/proj/runtime-EclipseApplication/Test/</project-dir>
<input-dirs>
<input-dir>test/conf/jca/</input-dir>
</input-dirs>
<output-dir>output/</output-dir>
</settings>
<targets>
<target id="dev" id-prefs="global, cat, dog"/>
</targets>
<files>
<file src="test/conf/jca/solid-ds.xml">
<cfg-file exclude="false" id="global" name="conf/jca/ds/solid-ds.xml"/>
</file>
</files>
<tokens>
<token name="ds">
<value form="complex" id="global" type="pre-install" use="mandatory"><![CDATA[jdbc
kk]]></value>
<value form="simple" id="dev" type="install" use="optional">ds.dev</value>
</token>
</tokens>
</grass-cfg>