sbt/sbt

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.

Sukant Hajra

@shajra

I see +, though.

Sukant Hajra

@shajra

(I found it).

Sukant Hajra

@shajra

cross-compiling is confusing me a lot.

Just when I think I understand how it's supposed to be set up, I run into something that doesn't work the way I'd prefer.

Sukant Hajra

@shajra

Does it make sense that it matters what order things are specified in .aggregate?

I'd have thought dependency resolution would make the order not matter.

eugene yokota

@eed3si9n

ordering in .aggregate should not matter

Dale Wijnand

@dwijnand

@vkostyukov that's sbt/sbt#2698

Kåre Blakstad

@kareblak

I'm using sbt docker. This task doesn't read any input, so I want a version of this task where an inputKey is being parsed and this value is set like (imageNames in docker).map(_.copy(tag = inputValue))... How can I accomplish something like that? This is a sbt docker example, but should be valid for all cases where one would like user input to non-input task.

Sukant Hajra

@shajra

Because of weirdness with "sbt-doge" and nested-aggregate projects, I'm bailing out on it. And I'm thinking I'll just make calls like this sbt '; ++ 2.12.2 ; clean ; test ; publish ; ++ 2.11.11 ; subproject/test ; subproject/publish'

Sukant Hajra

@shajra

So, if I use ++, and don't use + at all, then it seems that setting crossScalaVersions is needless?

Dale Wijnand

@dwijnand

yes

eugene yokota

@eed3si9n

also once you have the right sequence of commands down, you can implement your own release command like this - https://github.com/sbt/sbt/blob/249c1299a4deaf1756d12dce66e8eb477c719c75/build.sbt#L492-L500

Sukant Hajra

@shajra

@dwijnand @eed3si9n thanks for the confirmation. I'm so greatful that I at least can have explicit control. It's cute to have a + operator work out of the box, but I've got other problems to deal with if it doesn't.

Abhishek Jain

@jaina00

Hi... I have some common dependencies in all projects.

I am thinking of creating a new library and move the common ones to that library. And then import that new library to load the common dependencies and only have project specific dependency in each project.

Can you please point me to an example on how to best do it...

Rob Norris

@tpolecat

So, if I have compiling code and make a change that breaks something, then I undo my changes sometimes sbt just instantly says [success] Total time: ... without any [info] Compiling message. It's as if it has cached the previous good state. Am I imagining something?

It may only happen with ~compile, not sure.

@eed3si9n hate to bug you but it smells like the kind of thing nobody else would know ^

Dale Wijnand

@dwijnand

@tpolecat yeah if the reverted state hashes to the same value, the incremental compiler with match it with the already existing class files and not do any unnecessary work.

That said, of course incremental compiler bugs are a thing, so please report if you see errors.

Rob Norris

@tpolecat

@dwijnand cool, thanks. No errors, I was chasing down an issue with an editor plugin that seemed to correspond with that phenomenon.

Anthony Garo

@agaro1121

hey guys, when you call “reload” from within the sbt repl, does it discard the -Dparams passed in originally?

Dale Wijnand

@dwijnand

Anthony Garo

@agaro1121

thank you

Dale Wijnand

@dwijnand

no worries

eugene yokota

@eed3si9n

@tpolecat i think you are witnessing "transactional" classfile manager, which saves the old *.class filles related to the changed source in a temporary place before embarking on incremental compilation, and if the round of incremantal compilation results in an error, it places the old *.class files back. so if you undo right away, the round 2 of incremental would be no-op.

https://github.com/sbt/sbt-zero-thirteen/blob/v0.13.15/compile/inc/src/main/scala/sbt/inc/ClassfileManager.scala

Rob Norris

@tpolecat

Cool, thanks.

Naftoli Gugenheim

@nafg

Remind me how to iterate over setting values of all projects it's defined in?

I'm doing something similar to sbt-updates for npmDependencies

Dale Wijnand

@dwijnand

There's a .all on keys that you can pass a filter

Ryan Williams

@ryan-williams

probably dumb q: trying to run sbt console on a subproject, specifically core project in case-app:

$ sbt core/console
[info] Loading global plugins from /Users/ryan/.sbt/0.13/plugins
[info] Loading project definition from /Users/ryan/c/case-app/project/project
[info] Loading project definition from /Users/ryan/c/case-app/project
[info] Set current project to case-app-root (in build file:/Users/ryan/c/case-app/)
[error] No valid parser available.
[error] core/console
[error]      ^

confused why this doesn't work. this SO implies that it should.

also confused why regular sbt console in this project doesn't appear to have any of the project's classes (e.g. caseapp.core) import-able/available

Martin Duhem

@Duhemm

@ryan-williams that's a cross project, so you probably want to run ˋsbt coreJVM/consoleˋ instead.

Ryan Williams

@ryan-williams

@Duhemm interesting, thanks!

Tao

@sometao

Hi, there. I got UNRESOLVED DEPENDENCIES whith SNAPSHOT dependency on win10. anyone know what should I do?

sbt/sbt#3304

Any workaround here?

Naftoli Gugenheim

@nafg

I have a project with a lot of subprojects and every time I run testQuick I got lots of these:

[info] No tests were executed.
[info] No tests to run for views_common/test:testQuick
[info] Passed: Total 0, Failed 0, Errors 0, Passed 0

Seems annoying and unnecessary. Can it be eliminated?

Olli Helenius

@liff

@nafg that output seems to be from scalatest

shi gengtian

@shigengtian

For better performance, hit [ENTER] to switch to interactive mode,

how to fix this?

Olli Helenius

@liff

@shigengtian looks like the nag will be removed in 0.13.16

Derek Wickern

@dwickern

is it possible to return inside def taskImpl = Def.task[Unit] { ... } ?

Dale Wijnand

@dwijnand

most probably not

Han van Venrooij

@irundaia

What's the preferred way of making sure that your tests succeed before publishing?

I used to do publish := publish dependsOn(test in Test). But this doesn't seem execute anything :(

Dale Wijnand

@dwijnand

publish := (publish dependsOn (test in Test)).value

Where communities thrive

People

Repo info

Activity