new version not source compatible

[casualjim]

The package names have changed that means anything that uses this library (and there are many projects) now has to edit the source because of a change that's merely an implementation detail.

Can we please have the old package structure back?

I think if you alias LazyLogging or StrictLogging to Logging in this file: https://github.com/typesafehub/scala-logging/blob/master/scala-logging-slf4j/src/main/scala/com/typesafe/scalalogging/slf4j/Logging.scala

the balance will be restored and needless edits can be avoided. I would like to plead for source compatibility in a library as basic as logging.

[hseeberger]

Thanks for using Scala Logging in many projects and apologies for the trouble!

We can't have the old package structure and naming back, because there are already users of the new version 2.x. Of course these are breaking changes, but 2.x was a major release, so this should not be unexpected. Going forward I see more stability in terms of naming.

Logging won't be used as an alias for one of the two LazyLogging or StrictLogging in the library itself, because there shall be no bias. I suggest you do that in a top-level package object in your projects.

[rossabaker]

Yes, I've already created three top-level Logging traits for cross building purposes, when there need only be one: yours. A deprecation cycle would move toward removing the bias while supporting the people who still must support Scala 2.10.

I like the new API. I was happy with the old API. I'm frustrated that, as we transition from Scala 2.10 to 2.11, there is no version of this API supported by both Scalas. :(

[hseeberger]

I'm glad you like the API(s) and I'm sorry for the frustration.