These are chat archives for sbt/sbt

28th
Jan 2016
EastAnt
@EastAnt
Jan 28 2016 06:30
sbt coverageAggregate
[info] Set current project to target (in build file:/home/jenkins/workspace/ncrazer_dailybuilding/CrashCollector/target/)
[error] Not a valid command: coverageAggregate
[error] Not a valid project ID: coverageAggregate
[error] Expected ':' (if selecting a configuration)
[error] Not a valid key: coverageAggregate (similar: aggregate)
[error] coverageAggregate
[error] ^
sbt coverageAggregate is an invalid command?
Perry
@pfn
Jan 28 2016 06:33
why would you expect it to be a valid command?
EastAnt
@EastAnt
Jan 28 2016 06:53
I got two modules' coverage report generating with 'Scoverage'.But I need just one coverage report.Is there any way to aggregate the report to one report?I just found the way said that 'sbt coverageAggregate' could do so.
Perry
@pfn
Jan 28 2016 06:53
dunno what scoverage is
EastAnt
@EastAnt
Jan 28 2016 06:54
a plugin for SBT that integrates the scoverage code coverage library
EastAnt
@EastAnt
Jan 28 2016 07:01
So there is no command coverageAggregate for sbt?
Perry
@pfn
Jan 28 2016 07:03
not in sbt
it would come from a plugin
in this case, scoverage
EastAnt
@EastAnt
Jan 28 2016 07:05
OK,thx~
Fran├žois Garillot
@huitseeker
Jan 28 2016 09:29
@nafg I'll do something like this, thanks !
Ben McCann
@benmccann
Jan 28 2016 10:14
sbt-license-report is almost working now that 0.13.10-RC1 is out! sbt/sbt-license-report#24
Josh Suereth
@jsuereth
Jan 28 2016 14:04
@benmccann Awesome!
Sam Halliday
@fommil
Jan 28 2016 14:08
@benmccann I'll try to mention this at my licencing talk at scalasphere.org in a few weeks
Matt Hughes
@matthughes
Jan 28 2016 14:39

Upgraded from 0.13.9 -> 0.13.10-RC1 this morning and getting tons of these warnings:

[info] Resolving foo#sdk;2.0.0-SNAPSHOT ...
[warn] Unable to reparse foo#sdk;2.0.0-SNAPSHOT from maven-proxy-releases, using Thu Jan 28 09:26:20 EST 2016
[warn] Sorrting results from foo#sdk;2.0.0-SNAPSHOT, using Thu Jan 28 09:26:20 EST 2016 and Thu Jan 28 09:26:20 EST 2016
[warn] Sorrting results from foo#sdk;2.0.0-SNAPSHOT, using Thu Jan 2

Besides the spelling error which I can PR, what does this mean?

Mike Slinn
@mslinn
Jan 28 2016 19:32
SBT's classloader runs a second instance of SBT whose version is specified in build.properties. Which instance of SBT do SBT plugins pertain to?
Sam Halliday
@fommil
Jan 28 2016 19:38
what is PSA?
Matt Hughes
@matthughes
Jan 28 2016 19:39
public service announcement
Sam Halliday
@fommil
Jan 28 2016 19:39
Dale Wijnand
@dwijnand
Jan 28 2016 20:23
@mslinn are you quoting that from somewhere?
There only is one version of sbt running, the one specified in project/build.properties
nafg
@nafg
Jan 28 2016 21:30
It's a misunderstanding
@mslinn there aren't 2 instances of sbt, there is sbt-launcher.jar which has its own version, and there's the version of the actual sbt implementation
@mslinn usually launcher version X can run sbt version Y, but not for every X and Y
Dale Wijnand
@dwijnand
Jan 28 2016 21:37
until recently the launcher was a part of sbt, and versioned with sbt, so sbt-launcher version X always worked with sbt version X
oh actually that's still the case, we just repackage it and give it sbt's version
Mike Slinn
@mslinn
Jan 28 2016 22:23
@nafg So sbt-launcher starts SBT proper, and for the compile task at least 2 builds are initiated, one after the other, each with a unique instance of scalac. The user's code is built according to build.sbt, and the meta-project that builds the user code is built according to the defaults hardwired into the version of SBT that manages the whole shootin' match. Correct so far?
@nafg The meta-project might itself be built with a meta-meta-project ... and it is sbt all the way down
@nafg SBT 0.13.x does not allow the scalac version to be modfied for the meta-project. How am I doing so far?
OlegYch
@OlegYch
Jan 28 2016 22:48
meta-project allows that, but doesn't support..
doesn't support versions other than 2.10.x that is
Mike Slinn
@mslinn
Jan 28 2016 22:50
@OlegYch ... for SBT 0.13.9, that is
Perry
@pfn
Jan 28 2016 22:50
no version of sbt allows changing the scalaVersion of the meta project
OlegYch
@OlegYch
Jan 28 2016 22:50
for any 0.13.x version
Perry
@pfn
Jan 28 2016 22:50
not just 0.13.9
not just any 0.13.x
no version of sbt
OlegYch
@OlegYch
Jan 28 2016 22:50
it doesn't?
Mike Slinn
@mslinn
Jan 28 2016 22:50
As I said "according to the defaults hardwired into the version of SBT"
Perry
@pfn
Jan 28 2016 22:50
you can change it, but nothing will work
OlegYch
@OlegYch
Jan 28 2016 22:51
weird
ok though
Perry
@pfn
Jan 28 2016 22:51
you have ABI problems if you change it
OlegYch
@OlegYch
Jan 28 2016 22:51
with 2.10.x?
Perry
@pfn
Jan 28 2016 22:51
well, yeah, you can change to any .x version
any ABI compatible version, ok, point taken and refined :P
OlegYch
@OlegYch
Jan 28 2016 22:52
right
Perry
@pfn
Jan 28 2016 22:52
@mslinn there's nothing hardwared
sbt is just a scala library, and is subject to ABI issues with scala
Mike Slinn
@mslinn
Jan 28 2016 22:54
@pfn Perhaps better said as "meta-project defaults vary according to the version of SBT. For example, 0.13.9 defaults to scalac 2.10.5, but that can be changed to any version of scalac 2.10.x by specifying scalaVersion in project/build.sbt" ... is that correct?
Perry
@pfn
Jan 28 2016 22:55
yeah, that's reasonable
Mike Slinn
@mslinn
Jan 28 2016 22:56
So project/project/..../project/build.sbt is a meta-project to the nth power, and it can use any compatible compiler. For sbt 0.13.9, that is of course 2.10.x
Perry
@pfn
Jan 28 2016 22:59
probably, yes
Mike Slinn
@mslinn
Jan 28 2016 23:23
I updated our SBT Global Setup lecture. Thanks!
Ben McCann
@benmccann
Jan 28 2016 23:33
@jsuereth @fommil I fixed the other big problem I was running into with sbt-license-report - sbt/sbt-license-report#26