Allow enabling debug logs

[HoussemNasri]

Just pass --debug to the command line.

Mandatory checks

• Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (for UI changes)
• Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[koppor]

The idea is good. I saw, there already is a --debug switch:

jabref/src/main/java/org/jabref/cli/ArgumentProcessor.java

Line 190 in 6c680ea

if (!cli.isBlank() && cli.isDebugLogging()) {

The check for --debug has to be done very early (due to our "broken" argument handling).

Suggestion (because of code reuse)

• Remove these three lines (the if statement)
• Use JabRef CLI directly to parse the arguemnts and handle it.

[Siedlerchr]

we need to test the binary that comes out of this if it works

[HoussemNasri]

I tested it locally (on Linux) by creating an image with jlink, and the logs are written correctly to the selected log file.

[Siedlerchr]

xception in thread "main" java.lang.UnsupportedOperationException: Configuration cannot be changed after applying to tinylog
at [email protected]/org.tinylog.configuration.Configuration.set(Configuration.java:288)
at [email protected]/org.jabref.cli.Launcher.lambda$addLogToDisk$0(Launcher.java:124)
at java.base/java.lang.Iterable.forEach(Iterable.java:75)
at [email protected]/org.jabref.cli.Launcher.addLogToDisk(Launcher.java:124)
at [email protected]/org.jabref.cli.Launcher.main(Launcher.java:60)

[Siedlerchr]

Found the issue. It was the Localization.lang call

[HoussemNasri]

Oops, I didn't test it after using JabRefCLI