Refactor: Migrate from JUL to SLF4J API in SBMLinterpreter#110
Open
dyrpsf wants to merge 1 commit into
Open
Conversation
draeger
approved these changes
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR modernizes the logging framework in
SBMLinterpreter.javaby migrating from Java's built-injava.util.logging(JUL) to the SLF4J API. This aligns with the broader ecosystem goal of standardizing logging across the JSBML/SBSCL libraries (as discussed in JSBML Issue #217).Changes Made
java.util.logging.Loggerwithorg.slf4j.LoggerandLoggerFactoryinSBMLinterpreter.java.logger.log(Level, ...)to the SLF4J standardlogger.debug()andlogger.warn()methods, utilizing parameterized messages{}.slf4j-apidependency to the rootpom.xml.Validation