These are chat archives for sbt/sbt
A relaxed chat room about sbt (That interactive build tool). For getting help on sbt, we encourage people to document it on Stackoverflow or subscribing to Lightbend subscription.
sbt -Dfoo=barI always get
Warning: invalid system property 'foo'and exception. I have to call
sbt -D"foo=bar". Why?
1.0.0tag. I wanted to get launcher sources to debug this problem, but there is only
project/plugins.sbtto load plugins?
$ pausefeature in scripted, which gives you the directory?
build.sbtSBT hangs and waits for input from the console (q-quit, etc.). In forked test I cannot find, where is the console output redirected
coverage test coverageReport
sbt clean +coverage +test +coverageReport- no coverage data,
sbt clean +";coverage;test;coverageReport"- but it's not proper syntax,
addCommandAlias("mycov", ";coverage;test;coverageReport")and call
sbt clean +mycov- ignored
+sign and generated report for
sbt clean coverage +test coverageReport
coverageis a command toggiling boolean flag, with it turned on, the ode is instrumented. With your proposal, code is not instrumented at all (
+testdoesn't see the state changed by
coverage, like there was no
coveragecommand at all)
coverageReporttries to generate report for one Scala version only (but it skips, because there is no scoverage data)
;coverage;test;coverageReportsequence can properly use the same build state (it works now), there should be the way to fire multiple such sequences for different Scala versions, right?
+command followed by a task, like
test. But it won't work with
coverageas it's a command.
sbt clean coverage +mycov, where
mycovis defined as
mycov := Def.sequential(test in Test, coverageReport).valuebut it does not generate coverage info. My task doesn't see changes in build state made by