The LFET.Pro­ject.ini file

LFET.Pro­ject.ini and LFET.Project.yaml files are used to centrally define project settings for groups of decision tables, such as settings for the management of backup copies, defining storage directories and encodings for generated files, etc.

The following file names are allowed

Notes on LFET.Pro­ject.ini files

  • File names are case-insensitive.

  • Capitalization is also irrelevant for key names, as is the use of periods to separate words.

  • LFET.Pro­ject.ini files can also be nested, see: Multiple Pro­ject.ini files.

  • Settings that are intended to apply to exactly one decision table can be defined in two ways:

  • Examples: A specific class name, a particular Java package declaration, the targeted suppression of interval checks, etc.

  • LFET.Pro­ject.ini files are searched for backwards through the folder hierarchy, starting from the location of the decision table. See also: Search for Pro­ject.ini files.

  • Key names can also be used within key values, optionally enclosed in curly or square brackets, using the syntax ${key} or $[key] . Here is an example:

Entry in an LFET.Project.ini-file:
ide.Java.SourcePath = ${project.root}/../../java/${package}
Entry in an LFET.Project.yaml-file:
ide.Java:
  SourcePath: ${project.root}/../../java/${package}

  • Important note: For multi-level path specifications "/" must be used instead of "\" as a separator, i.e. not Java\Source but: Java/Source.

  • For relative paths, the location of the Project.ini file is used as the basis for forming the absolute path.

  • If required, you can also define your own keys in the decision tables themselves both in the LFET.Pro­ject.ini files and using the syntax $$key=value. The definition of own keys in decision tables is created in the same way as the definition of language-related generation parameters.

  • Key definitions in decision tables overwrite same name definitions from LFET.Pro­ject.ini files.

Contents of this chapter