You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the installation file (installation.xhtml.vm) the description of the logback.xml property says "The file ids.logback.xml.example may be renamed to ids.logback.xml to get started” but the file is actually called logback.xml.example and can be renamed to logback.xml.
I'm not actually sure this property works. Sam Hough in Diamond had problems with the property and asked me about it which alerted me to the error in the documentation. So possibly this property needs removing from the documentation and instead have a sentence in the instructions telling you to rename the file if you want to use it.
The text was updated successfully, but these errors were encountered:
Looking into this a bit further, there is no code to handle a logback.xml property in the PropertyHandler (or anywhere else in the java code). The only place the file is handled is in the setup script where if a file named logback.xml is found then it is added to the WEB-INF/classes directory of the jar to be deployed.
Therefore I think the correct thing to do is to remove the documentation of the property in the run.properties file and add a sentence to the instructions saying to rename the file if you want to use it.
In the installation file (installation.xhtml.vm) the description of the logback.xml property says "The file ids.logback.xml.example may be renamed to ids.logback.xml to get started” but the file is actually called logback.xml.example and can be renamed to logback.xml.
I'm not actually sure this property works. Sam Hough in Diamond had problems with the property and asked me about it which alerted me to the error in the documentation. So possibly this property needs removing from the documentation and instead have a sentence in the instructions telling you to rename the file if you want to use it.
The text was updated successfully, but these errors were encountered: