These are chat archives for sbt/sbt

3rd
Jun 2017
Jorge
@jvican
Jun 03 08:46
@BardurArantsson If you're using sbt 0.13.x, I strongly suggest you use sbt-doge :) There are some problems with + in sbt, and that's why sbt-doge is recommended.
In sbt 1.0.x, sbt-doge has been ported to upstream sbt, so it will be enabled automatically.
Looking forward to more questions!
Bardur Arantsson
@BardurArantsson
Jun 03 08:47

:)

Ok, so for any project that cross-builds, basically?

Jorge
@jvican
Jun 03 08:47
Yeah
Bardur Arantsson
@BardurArantsson
Jun 03 08:48
Cool, thanks.
Jorge
@jvican
Jun 03 08:48
:D welcome
Bardur Arantsson
@BardurArantsson
Jun 03 08:48
Will do from now on. :)
Merlijn Boogerd
@mboogerd
Jun 03 16:00
I have only just discovered sbt new this weekend during Scala Days and decided to then finally refactor my custom scala seed to a giter8 template. Everything is pretty smooth, but I run into one problem. The "maven" properties , that allow one to fetch the latest stable version of dependencies don't get evaluated with sbt new, whereas they get evaluated just fine when I run sbt g8 manually from within the scala-seed project. Does anybody have a clue why this might happen?
For who would want to have a look in detail, this is the current state of the seed: https://github.com/mboogerd/scala-seed.g8
Perhaps to be more clear, by "not evaluated" I mean they get printed literally, as follows:
"commons-io" % "commons-io" % "maven(commons-io, commons-io, stable)"
Nicolas Rinaudo
@nrinaudo
Jun 03 16:26
Is this the most up-to-date documentation on sbt-scripted? http://eed3si9n.com/testing-sbt-plugins
it's the only I could find, but it's from 2011
(it might just mean that it was so good and exhaustive that there was no need to update it, I don't mean to say that its age necessarily makes it obsolete)
marios iliofotou
@imarios
Jun 03 23:24
@mboogerd I think sbt new uses a different version than running g8