You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
adding the scrooge sbt plugin causes sbt to import all of it's keys into the namespace of a built.sbt file. so in build.sbt, the top of the file magically receives:
this becomes a problem when you want to have target specific settings, for example:
// in build.sbt
wartremoverErrors in (Compile, compile) ++=Seq(...)
// compile error://// .../build.sbt:43: error: reference to compile is ambiguous;// it is imported twice in the same scope by// import _root_.com.twitter.scrooge.ScroogeSBT._// and import Keys._// wartremoverErrors in (Compile, compile) ++= Seq(...)
as a temporary workaround, you can do:
// at the top of build.sbtimportKeys.{compile=>sbtCompile}
...
wartremoverErrors in (Compile, sbtCompile) ++=Seq(...)
renaming the function in scrooge should fix it.
The text was updated successfully, but these errors were encountered:
matthandlersux
changed the title
compile function in ScroogeSBT conflicts with sbt.Keys.compile
compile function in ScroogeSBT conflicts with sbt.Keys.compile
Oct 15, 2015
matthandlersux
changed the title
compile function in ScroogeSBT conflicts with sbt.Keys.compile
"compile" function in ScroogeSBT conflicts with sbt.Keys.compile
Oct 15, 2015
adding the scrooge sbt plugin causes sbt to import all of it's keys into the namespace of a
built.sbt
file. so inbuild.sbt
, the top of the file magically receives:this includes the
compile
function here: https://github.com/twitter/scrooge/blob/develop/scrooge-sbt-plugin/src/main/scala/com/twitter/ScroogeSBT.scala#L13 , but it collides with https://github.com/sbt/sbt/blob/1.0.x/main/src/main/scala/sbt/Keys.scala#L188this becomes a problem when you want to have target specific settings, for example:
as a temporary workaround, you can do:
renaming the function in scrooge should fix it.
The text was updated successfully, but these errors were encountered: