These are chat archives for sbt/sbt

11th
Sep 2015
Perry
@pfn
Sep 11 2015 00:53
how is the order of scripted tests determined? it's not alphabetical....
the order of listFiles?
Perry
@pfn
Sep 11 2015 01:02
so weird, running a scripted test in one test set creates a directory in another source set, wtf
Ferdinand Svehla
@fsvehla
Sep 11 2015 08:30
Where would I go about to set triggeredMessage := Watched.clearWhenTriggered for every project that I work on on this machine? ~/.sbt/global would run before projects are loaded so could not set settings, right?
Perry
@pfn
Sep 11 2015 15:48
  def kotlinLib(name: String) = Def.setting {
    "org.jetbrains.kotlin" % ("kotlin-" + name) % kotlinVersion.value
  }

  def kotlinPlugin(name: String) = kotlinLib(name)(_ % "provided")
does this do what I expect?
I assume yes
(I can use kotlinPlugin the same way kotlinLib is used)
Seth Tisue
@SethTisue
Sep 11 2015 16:27
@dpennell unclear on your question. what kind of file is this tar.gz file and in what sense do you want to include it in your build? also, it might help to see what you tried, both what you put in your build configuration, and what error your are getting
if it’s .tar.gz and not .jar, what does it even mean to “resolve” it in the Maven sense?
Richard Gomes
@frgomes
Sep 11 2015 18:50
Hello. I'd like to create a configuration which adds exportJars := true to the root project. I did that in the hope that show MyConfig:dependencyClasspath lists all dependencies as .jar files... but it only lists the root jar file and scala library. Thoughts?
Richard Gomes
@frgomes
Sep 11 2015 19:00
@pfn :: no... no... exportJars := false by default... but I was setting it true by copy/paste/mistake from another build. The issue is... if you do exportJars := true, your /src/main/resources and /src/test/resources will be packaged inside a .jar file and this was breaking my test cases which are dependent on resources sitting on the file system (not packaged inside jars).
Perry
@pfn
Sep 11 2015 19:01
because exportJars doesn't apply to all projects
set projectJars in Global
maybe
Richard Gomes
@frgomes
Sep 11 2015 19:03
@pfn :: I need exportJars := false in general but I need a special configuration which packages everything (not a fatjar!) and list all dependencies as .jar files.
David Pennell
@dpennell
Sep 11 2015 19:11
@SethTisue I sent all of the details in via one of our Typesafe subscriptions...
Richard Gomes
@frgomes
Sep 11 2015 19:15
@pfn :: Seems like the problem I'm facing is that I need to define a configuration inside project root which is the same as root itself, plus some more stuff. But I cannot do that inside root itself.
Perry
@pfn
Sep 11 2015 19:16
that just made no sense
Seth Tisue
@SethTisue
Sep 11 2015 19:20
@dpennell cool, you should hear from someone whose sbt wizard hat is considerably taller than my own
Perry
@pfn
Sep 11 2015 19:59
I'm confused why @dpennell is having a problem, shouldn't it be as simple as specifying artifact type in libraryDependencies?
of course, when it's published to artifactory, it should have all the correct ivy/pom associated still
e.g. if deploying with maven, mvn deploy:deploy-file -DartifactId=basename -Dfile=yourfile.tar.gz -DgroupId=yourgroup -Dpackaging=tar.gz