I think there is some misconfiguration on jppf-client pom file (or actually jppf-common, on which client depends).
When importing jppf client - transitive dependencies bring into runtime scope slf4j-log4j bridge and log4j itself - and I think this should be avoided with libraries.
Decision which logging library to use should be left to parent application that uses jppf-client.
JPPF Driver/node/monitor can use log4j if they like it, but my application also uses slf4j, but we are not using log4j - and in order to avoid
conflicts we always have to exclude those dependencies manually.
marcin
