Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
72:local_message_custom [2018/09/27 18:14] – [Local Message Customization] emr72:local_message_custom [2020/08/21 10:10] – sahr
Line 7: Line 7:
 Each message possesses a standard definition which can be overwritten by local definitions. These local messages can be configured in the file ''<font inherit/Courier New,Courier,monospace;;inherit;;inherit><STAGESHOME>/conf/local.properties</font>''  and its localized versions (e.g. ''<font inherit/Courier New,Courier,monospace;;inherit;;inherit><STAGESHOME>/conf/local_de.properties</font>''). At system startup, your messages will be automatically merged into the message pool of Stages. Each message possesses a standard definition which can be overwritten by local definitions. These local messages can be configured in the file ''<font inherit/Courier New,Courier,monospace;;inherit;;inherit><STAGESHOME>/conf/local.properties</font>''  and its localized versions (e.g. ''<font inherit/Courier New,Courier,monospace;;inherit;;inherit><STAGESHOME>/conf/local_de.properties</font>''). At system startup, your messages will be automatically merged into the message pool of Stages.
  
-The format of the message files conforms to the Java property files standard ("name = value"). Detailed information concerning the definition of messages can be found in the Stages Metamodeling Guide document.+The format of the message files conforms to the Java property files standard ("name = value").