New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use SLF4J for logging #155
Comments
+1, and biojava-legacy too. Just make sure that the only compile time dependency is on slf4j-api. There may be a test scoped dependency on say slf4j-simple for logging during unit tests. |
- added runTime scope binding for log4j2 since it's the one logger framework that was used already elsewhere. We even had already some config files for it in the structure module - added the safe config to all poms of modules. Config files for log4j2 are only in the structure module. Other modules will have to add config files if needed - default level in config files set to: warn for run, info for test - moved logging in the PDB parser to slf4j
Test configuration uses INFO and production uses WARN
Convert core package to use slf4j #155
Convert aaproperties and alignment packages to slf4j #155
Convert org.biojava3.genome to slf4j #155
- some improvement in exceptions and logging biojava#111 and biojava#155
- some improvement in exceptions and logging biojava#111 and biojava#155
Updated packages to use slf4j for logging #155
- also improvements for biojava#111 and biojava#155 - some more work to do to make sure AtomCache and the Readers don't double read the environment variables/system properties
- reduced the number of initialisations in AtomCache and readers - now all chem comp providers use PDB_CACHE_DIR - a few biojava#111 and biojava#155 fixes
- some improvements for biojava#111, biojava#155 and biojava#185
can we close this? |
Indeed there's been enormous progress in this. But I'd say that the structure package needs some more work, there's still quite a few hidden prints to stdout/stderr. Let's give it a bit more time. |
Update org.biojava.bio.structure (main) package in biojava3-structure project to use slf4j #155
- also some improvement for biojava#191: now a TranslationException will be thrown when compound not known - a few improvements for other issues: biojava#111, biojava#155, biojava#185
How about now, @josemduarte? Logging doesn't change the API, so it can easily go out in patch commits. |
Yep let's close it, I think the logging coverage now is quite decent. Surely there must be some other places with missing logging but we can add more commits later |
Re-opening this for now so that I can reference it in commits. |
…ied some code, made clone() call super.clone(), and switched from StringWriter and StringBuffer to the faster (asynchronous) StringBuilder.
…ied some code, made clone() call super.clone(), and switched from StringWriter and StringBuffer to the faster (asynchronous) StringBuilder. Small improvements to rcsb package and to Astral class.
…ied some code, made clone() call super.clone(), and switched from StringWriter and StringBuffer to the faster (asynchronous) StringBuilder. Small improvements to rcsb package and to Astral class.
…ied some code, made clone() call super.clone(), and switched from StringWriter and StringBuffer to the faster (asynchronous) StringBuilder. Small improvements to rcsb package and to Astral class.
…ied some code, made clone() call super.clone(), and switched from StringWriter and StringBuffer to the faster (asynchronous) StringBuilder. Small improvements to rcsb package and to Astral class.
Can't you reference a closed issue? jose's commits seem to have been picked up after it closed. |
Yes, apparently I can! (I didn't know.) |
I believe we reached a consensus on the mailing list to use slf4j for logging, due to its easy interoperability with other logging frameworks.
Todo:
anymany of these)This would be a great project for someone trying to start contributing to BioJava.
The text was updated successfully, but these errors were encountered: