Project

General

Profile

Actions

Bug #4362

closed

JWt POM depends on slf4j-simple

Added by Jonas Hauquier over 10 years ago. Updated 14 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
07/29/2015
Due date:
% Done:

100%

Estimated time:

Description

The jwt-3.3.4.pom file lists slf4j-simple explicitly as dependency. This causes any maven project to depend on jwt to have the slf4j simple logger back-end in their classpath. In my case, this interfered with my choice of using logback as back-end for my application, because slf4j loads whatever logging back-end it encounters first in the classpath.

To get around this issue I had to modify the jwt pom file and mvn install jwt with this non-default pom file.

In my opinion, the choice of logging back-end should be left to the application creator, and should not be decided by the ui framework that's included. That's why I consider this a bug.

Actions #1

Updated by Matthias Van Ceulebroeck 15 days ago

  • Description updated (diff)
  • Status changed from New to InProgress
  • Assignee set to Raf Pauwels
  • Target version changed from 3.3.4 to 4.12.1
Actions #2

Updated by Matthias Van Ceulebroeck 15 days ago

  • Category deleted (Deployment)
  • Status changed from InProgress to Review
  • Assignee changed from Raf Pauwels to Matthias Van Ceulebroeck
Actions #3

Updated by Matthias Van Ceulebroeck 15 days ago

  • Status changed from Review to Implemented @Emweb
  • Assignee changed from Matthias Van Ceulebroeck to Raf Pauwels
  • % Done changed from 0 to 100
Actions #4

Updated by Matthias Van Ceulebroeck 14 days ago

  • Status changed from Implemented @Emweb to Closed
Actions

Also available in: Atom PDF