Could we get the current master tagged for v2.1.1.6 or something so its more official looking? Currently I am getting the jar from jitpack.io but referencing the hash code for the current tip of master.
Master is good (no reference to vulnerable Log4J):
(I originally wrote this in #56 , but realized it was a closed PR and probably no one will see it, Reposting here so it is a live issue)
The update from #56 - it actually has us avoid the new log4j bug
https://mvnrepository.com/artifact/org.slf4j/slf4j-log4j12/1.7.12 https://www.cisa.gov/uscert/apache-log4j-vulnerability-guidance
Could we get the current master tagged for v2.1.1.6 or something so its more official looking? Currently I am getting the jar from jitpack.io but referencing the hash code for the current tip of master.
Master is good (no reference to vulnerable Log4J):
vs v2.1.1.5 which does reference Log4J:
So v2.1.1.5 contains:
And Log4j v1.2.17 --> https://mvnrepository.com/artifact/log4j/log4j/1.2.17...
So yeah - let's make the current master a version such as 2.1.1.6 so it can be referenced in a more official looking manner on jitpack.