maltcms.sh does not set maltcmsDefaultConfig
Brought to you by:
nilshoffmann
If maltcms.sh is called from a different location than the installation directory, the default configuration can not be resolved, leading to downstream errors in pipeline processing. This is due to maltcmsDefaultConfig not being set in the script. Reported by tplacht.
Anonymous
Fixed in 1.2.1.
Also applied to maltcms.bat.
Last edit: Nils Hoffmann 2012-09-18
Diff: