(followup from https://projects.tigase.org/issues/6006#note-8)

Andrzej Wójcik wrote:

And as for:

IMHO if we set --config-file old configuration detection and conversion shouldn't be run (which could override the config?)

I think that we should not treat it in any different way, as %kobit suggested, people are not familiar with DSL and may want to modify properties file and want Tigase to convert it to DSL once again.

If we would disable conversion of config file when --config-file is passed, then it would not be possible to force converter to read from one place and write the result in the other. So converter would be forced to write the same directory as init.properties file was locate, which could be marked as read-only on some installations.

Maybe a middle way?

Currently we have following options:

• --properties-file= - will trigger conversion and write config.tdsl

• --config-file= - will still check for init.properties file and if found try to convert it (if I understand it correctly, log entry OldConfigHolder.detectPathAndFormat() FINEST: No property file not specified would suggest it)?

My suggestion was, that if we have only --config-file (then someone is aware of the new config, migrated to it, etc) we don't detect properties file. However - we could support both --config-file and --properties-file so if the latter is present it would convert it to --config-file defined in the configuration option (and without it it would use default path).

In principle I think that simply sticking with using --properties-file would fulfil %kobit requirement (and if someone has odd installation with locked write then… this is no installation to experiment with configuration IMHO, and secondly - you could specify --config-file in writeable location to achieve same result).