java.lang.RuntimeException: Settings logger used after project was loaded.
at scala.sys.package$.error(package.scala:27)
at sbt.LogManager$$anon$1$$anonfun$slog$1.apply(LogManager.scala:110)
at sbt.LogManager$$anon$1$$anonfun$slog$1.apply(LogManager.scala:110)
at scala.Option.getOrElse(Option.scala:120)
at sbt.LogManager$$anon$1.slog(LogManager.scala:110)
at sbt.LogManager$$anon$1.log(LogManager.scala:115)
at sbt.Logger$class.info(Logger.scala:117)
at sbt.LogManager$$anon$1.info(LogManager.scala:108)
at com.typesafe.conductr.sbt.ConductR$$anonfun$com$typesafe$conductr$sbt$ConductR$$doLoadBundle$1$1.apply(ConductR.scala:39)
at com.typesafe.conductr.sbt.ConductR$$anonfun$com$typesafe$conductr$sbt$ConductR$$doLoadBundle$1$1.apply(ConductR.scala:38)
This is due to using sLog as the logger. It looks like Josh fixed this in 0.13.8
However: wouldn't it be better to just use
state.log.info("yadda")
instead of passing this logger through?
I've tested this and it works. I can create a PR tomorrow 9AM (-4 UTC)
Steps to reproduce:
cd into sbt-conductr-tester sub project
changes build.properties to:
try to load a bundle to a conductr server:
This is due to using sLog as the logger. It looks like Josh fixed this in 0.13.8
However: wouldn't it be better to just use
instead of passing this logger through?
I've tested this and it works. I can create a PR tomorrow 9AM (-4 UTC)