A relaxed chat room about sbt (the interactive build tool). Also good for sbt help: Stack Overflow, or Lightbend subscription. https://www.scala-sbt.org/support.html has advice on where to go.
in production I want to point to a different logbook.xml than the one I have in resources dir. Any tips how I would do this in my build.sbt?
tried:
javaOptions in assembly += "-Dlogback.configurationFile=" + logbackConfigPath
where
logbackConfigPath is the path to the logback.xml
and it didnt work
just manually making prs to the services bumping their version numbers or is there a plugin or something I am missing?
an example I could dig up was from my blog post - http://eed3si9n.com/sequencing-tasks-with-sbt-sequential
that will return Either to capture the error
@shajra it's for a bit of a weird project, but scala meta. I'm trying to do some code generation with scalafix, and for debugging purposes, it's nice to have access to scala meta in the sbt console. But I don't really want to include it in my builds, since it's only used for development
The ruby/bundler use cases are a bit more obvious, tools like pry for debugging aren't necessary for production purposes, but are nice to have for development. Not sure if there's anything like pry in scala, but that would be another good use for development only libraries in sbt
I'm about to dig into SBT source/docs... but is there an "inScope" shorthand for
inTask(compile)(inConfig(Compile)(...))?
you can define the scope you want and use
inScope or just do what you're already doing
like we do with "in"
Wait would it be
inScope(This in (Compile, compile)) { ... }?
I prefer
ThisScope instead of conflating scope component with a scope
but I think you got it
yeah, I don't know the hierarchy still.
but there's a stupid implicit conversion that converts from This to ThisScope that I hate
i am mad about
Global enough, that I've renamed it to Zero
so
GlobalScope = (Zero, Zero, Zero, Zero)
