Instantiationerror when using with scala-logging

[concerned3rdparty]

After sbt assembly , when i try to run the app from jar , it gives the error below .Is this about dependency version conflict? Any suggestions for the problem?
dependencies:
libraryDependencies += "com.softwaremill.reactivekafka" %% "reactive-kafka-core" % "0.10.0"
libraryDependencies += "com.typesafe.scala-logging" %% "scala-logging" % "3.1.0"
libraryDependencies += "ch.qos.logback" % "logback-classic" % "1.1.3"

Exception in thread "main" java.lang.InstantiationError: com.typesafe.scalalogging.Logger
at com.typesafe.scalalogging.Logger$.apply(Logger.scala:31)
at com.typesafe.scalalogging.LazyLogging$class.logger(Logging.scala:28)
at io.tazi.featureengineering.FeatureEngineering.logger$lzycompute(FeatureEngineering.scala:24)
at io.tazi.featureengineering.FeatureEngineering.logger(FeatureEngineering.scala:24)

[13h3r]

Looks like version of scala logging that we use in reactive kafka already deprecated. We use "com.typesafe.scala-logging" %% "scala-logging-slf4j" % "2.1.2", but now 3.1.0 available and artifact id named "com.typesafe.scala-logging" %% "scala-logging".

@kciesielski I see no reason to keep this version and suggest to use new one. What do you think?

[kciesielski]

@13h3r We kept 2.1.2 because 3.x was not compatible with Scala 2.10. As we switched to Scala 2.11, we should also switch to scala-logging 3. However, until it's released, it looks like reactive-kafka users also have to work with scala-logging-slf4j % 2.1.2 because 3.x is not backward compatible. Unless there's some kind of bridge that I'm not aware of?

[13h3r]

Got it. First of all lets ensure that problem is in scala logging version.
@concerned3rdparty could you try to build it with "com.typesafe.scala-logging" %% "scala-logging-slf4j" % "2.1.2"?

[kciesielski]

Ok, I'm preparing a PR in the meantime (#100)

[concerned3rdparty]

"com.typesafe.scala-logging" %% "scala-logging-slf4j" % "2.1.2" seems to work fine when running both from sbt and jar .

[kciesielski]

@concerned3rdparty Doesn't that break your own logging code? Can you show some examples how you import/use scala logging?

[concerned3rdparty]

After a change in import statement , it worked for version "2.1.2".

import com.typesafe.scalalogging.slf4j.LazyLogging

object A extends  App with LazyLogging{
    logger.info("nothing")
}

[13h3r]

Please leave comment if any