JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-550  -  log4j dependency in jppf.commons
Posted Oct 08, 2018 - updated Oct 15, 2018
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     zorba128
  • Owned by
    Not owned by anyone
  • Category
    Build
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Low
  • Targetted for
    icon_milestones.png JPF 6.0.1
Issue description
When trying to use JPPF client library log4j gets sucked into project by transitive dependencies.

Rather than that - jppf client (or - to be more specific - jppf commons) should depend on slf4j api only, leaving decision of which logger binding to use to client application.

So from dependencies below all but first should be removed.
<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-api</artifactId>
    <version>1.7.25</version>
</dependency>
<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-log4j12</artifactId>
    <version>1.7.25</version>
    <scope>runtime</scope>
</dependency>
<dependency>
    <groupId>log4j</groupId>
    <artifactId>log4j</artifactId>
    <version>1.2.15</version>
    <scope>runtime</scope>
</dependency>
If node/driver/web ui/admin ui want to use log4j for logging - it should become their runtime dependency.
Steps to reproduce this issue
see jppf-common's descriptor.