Hi all,
After spending 5 months working on real world commercial Scala / Akka / Spray, I wrote up some lessons learnt
One of the biggest lessons was how to get Logging set up in Scala. This is basically a mess at the moment (although there is already improvement in SBT and Specs2 as a result of the above) because there is no adopted logging API standard ... but the Akka LoggingAdapter could be it.
I'd really like you all to consider adopting the Akka LoggingAdapter trait as part of Scala Library, and providing a Java Util Logging (JUL) backend (there is one in akka-contrib... could do with a rename) for people to use out of the box.
I raised this as a ticket in the Akka issue tracker and they feel this is something they would support:
... all it needs is some consensus on the Scala side.
My concern is that logging in Scala is going to go the route of Java and we're going to end up with loads of conflicting third party libs all doing something that is essentially trivial. Compound that with the myriad of Java backends (SLF4J sometimes causes more problems than it creates) and things get really ugly.
I don't really care much for pushing JUL itself (it works, but don't ever look inside it or you might scream!). I would just like solidarity in one client-side logging API. JUL has the advantage that it is already shipped with J2SE, but I'd be equally happy if you went with SLF4J... compatibility with legacy Java libs is essential.
Best regards,
Sam