remove slf4j dependency? about jjwt HOT 4 CLOSED

+1
Since JJWT is a library that ideally would be referenced from a wide variety of execution contexts (JEE, standalone, Spring containers, OSGi containers (ok, OSGi doesn't have this problem)), dependencies should be kept to an absolute minimum. If SLF4J was embedded everywhere in JJWT, I would wipe my brow and bear it. But it seems that by simply (pun intended) logging to the JUL Loggers in the one class mentioned by @arvinsuresh , we could avoid yet another dependency.

Full disclosure: I worked with Arvin for a few months last Spring where we used JJWT. So my post stems from a common issue we both experienced on the same project task. But I expect this issue to reoccur with other teams I encounter. I'm a big fan of JJWT and nixing this extra dependency would really help to spread it.

from jjwt.

Yeah, this was an artifact from a copy-n-paste operation long ago. I'm happy to remove it since it's not prolific in JJWT and only used in one class. Thanks for the issue!

from jjwt.

+1
Android users try to stay under a function limit of 65k, so removing unnecessary dependencies would be nice.

from jjwt.

Resolved by PR #41. Will be released in 0.6.

from jjwt.