jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From woonsan <>
Subject [GitHub] jmeter pull request #274: Bug 60564 - Migrating LogKit to SLF4J - components...
Date Sat, 11 Feb 2017 07:06:27 GMT
GitHub user woonsan opened a pull request:

    Bug 60564 - Migrating LogKit to SLF4J - components (1), functions, protocol, test

    Migrated old logger to slf4j logger in functions, protocols and test.
    Also, applied the same backward compatibility pattern in AbstractBackendListenerClient
(in components) as done in AbstractJavaSamplerClient by @pmouawad with slightly changing logger
variable names. Preferred using 'log' for the new slf4j logger instance and named the old
logger to 'oldLogger' since 'log' variable name for slf4j logger is use everywhere.

You can merge this pull request into a Git repository by running:

    $ git pull feature/bz60564-13

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #274
commit 5eceb32e375a12345c395c7174bcfeb0a15db5f3
Author: Woonsan Ko <>
Date:   2017-02-11T07:00:28Z

    Bug 60564 - Migrating LogKit to SLF4J - components/ABLC, functions,
    protocol, test


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message