These are chat archives for sbt/sbt

17th
Dec 2015
Perry
@pfn
Dec 17 2015 02:21
@fommil, normal users universally hate scala build files
@fommil, sbt isn't applicable only to scala
and for that reason, allowing sbt files as the primary format is beneficial
and yes, intellij supports sbt files fully
andy scott
@andyscott
Dec 17 2015 09:59
Is there any way to get the autoImport for auto plugins to work in a full .scala build definition?
To automatically be imported, that is.
Sam Halliday
@fommil
Dec 17 2015 13:45
@andyscott just explicitly import them
It is not valid Scala otherwise
Dale Wijnand
@dwijnand
Dec 17 2015 14:06
it's one of the benefits of using .sbt files - no need to know the fully qualified class name for plugin settings etc
andy scott
@andyscott
Dec 17 2015 14:17
:thumbsup: Makes sense. It seems like as .sbt files become increasingly powerful, there’s a lot less of a need for full .scala build definitions
Dale Wijnand
@dwijnand
Dec 17 2015 14:19
Defining your build in .scala is kind of discouraged/deprecated. Using .scala files for utilities etc isn't (and encouraged, given it provides a gentle slope to creating standalone sbt plugins)
andy scott
@andyscott
Dec 17 2015 14:20
That’s the vibe I’ve been getting recently. Previously (years ago), I recall being unable to definel multi project builds in .sbt files. But that’s no longer the case.
Dale Wijnand
@dwijnand
Dec 17 2015 14:26
yeah I know. Once blank line separators requirement was dropped (especially not being able to use blank lines in methods!) I switched.
Only thing I'm missing is extention methods (implicit classes) in .sbt files.. but I've never looked at that part of the code and/or got furious enough to start :)
andy scott
@andyscott
Dec 17 2015 14:28
Is there any way to define stuff in one .sbt file, and then import or reference it easily in another?
I modeled most of my .scala build definitions after Spray’s repo, which has an object Dependencies in Dependencies.scala and then imports it in Build.scala.
I’d like to do something similar with .sbt files, if possible.
Dale Wijnand
@dwijnand
Dec 17 2015 14:33
looks like no
Perry
@pfn
Dec 17 2015 16:43
hmm
Sam Halliday
@fommil
Dec 17 2015 17:21
Is there a way to disable the dependency on precompiled compiler jars?
I think this involves providing a custom config to the launcher
Sam Halliday
@fommil
Dec 17 2015 17:27
I can't actually find what pulls the precompiled jars in. It's not a dependency of SBT or the launcher
Sam Halliday
@fommil
Dec 17 2015 17:46
(Our build of SBT anyway. No refs in the poms)
Sam Halliday
@fommil
Dec 17 2015 17:52
OK, solved it. Cache was getting in the way.
Dale Wijnand
@dwijnand
Dec 17 2015 18:20
do share :)
Sam Halliday
@fommil
Dec 17 2015 20:12
@dwijnand it was literally just a case of a bad cache. ~/.sbt/tmp seemed to store references to an early build that I'd made.
Removing the precompiled dep is as simple as removing the artefacts from build.sbt in SBT
Dale Wijnand
@dwijnand
Dec 17 2015 20:20
ok
Michael Pilquist
@mpilquist
Dec 17 2015 23:49
what’s the best option for proguard these days? still addSbtPlugin("com.typesafe.sbt" % "sbt-proguard" % "0.2.2")?
Sam Halliday
@fommil
Dec 17 2015 23:52
@mpilquist if you get it to work with anything that uses scala-compiler please let me know, we want to use it in ENSIME
Michael Pilquist
@mpilquist
Dec 17 2015 23:57
i use it in https://github.com/cjmx/cjmx but i ran in to major issues upgrading from sbt 0.11 to 0.12 to 0.13