Date: Thu, 28 Mar 2024 23:05:33 +0100 (CET) Message-ID: <319469049.1211.1711663533910@confluence-public.open-xchange.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1210_505178881.1711663533910" ------=_Part_1210_505178881.1711663533910 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Af= fected version(s): all
You have added a comment behind a config option, e.g.
com.openexchange.capability.mycapability=3Dtrue # Turn on awesome capa= bility
within a .properties file but the value doesn't work like expected.
Backend just utilizes "java.util.Properties" class to read .properties f= iles and assumes its author obeyed the Properties File Format , see:
Appending comments after property values would break nearly every non-st= ring property. Hence having a working properties file comments must not be = added after config option on the same line.