Refine documentation on logging #8550
Conversation
koppor
added
the
status: ready-for-review
| @@ -1,2 +1,3 @@ | |||
| level = info | |||
| writer = console | |||
| level@org.jabref.model.entry.BibEntry = debug | |||
There was a problem hiding this comment.
Is this only meant as an example, or actually desired?
There was a problem hiding this comment.
I wanted to choose a class not having extensive debug statements. I wanted to keep a line directly working. Think of novices not sure about comment characters in .properties file etc.
There was a problem hiding this comment.
And we reference it in the udpated howto:
In the
.propertiesfile, this is done fororg.jabref.model.entry.BibEntry.
There was a problem hiding this comment.
Are comments in a properties file allowed? If yes, it would be nice to give a few examples (i.e. activate debug logging for a particular class, for a module, for everything).
There was a problem hiding this comment.
Hash character #this is a comment work
* upstream/main: Update RemoteSetupTest.java, adding eq() function from mockito (#8561) readd encoding after merge Open office refactor finalization (formerly OObranch J cleanup) (#7795) Revert "Refine documentation (#8551)" (#8560) Refine documentation on logging (#8550) Revert "Refine documentation (#8551)" (#8559) Refine documentation (#8551) New Crowdin updates (#8557) New Crowdin updates (#8553) Fix missing metadata in BibDatabaseContext (#8556) Add encoding detection (and pin export to UTF-8) (#8506) Add Missing Fillers/Extractors for Supported Fields and Support Day Conversion (#8531) Bump checkstyle from 9.3 to 10.0 (#8544) Fix online link detection in entry editor (#8514) Add some JavaDoc to Fetchers Support two argument form of \abx@aux@cite macro in DefaultAuxParser (#8549)
We switched to tinylog. This PR fixes the documentation.
CHANGELOG.mddescribed in a way that is understandable for the average user (if applicable)