These are chat archives for sbt/sbt

28th
Jun 2016
Jonathan Ferguson
@jonoabroad
Jun 28 2016 00:41
Hello, is it possible to define a default mainClass in a multi project sbt build?
Jonathan Ferguson
@jonoabroad
Jun 28 2016 00:42
That doesn't appear to answer for a multi project sbt build.
Dale Wijnand
@dwijnand
Jun 28 2016 00:43
set the setting in the relevant project that contains the main
Jonathan Ferguson
@jonoabroad
Jun 28 2016 00:45
that will set the main for the sub project but not the build overall
Dale Wijnand
@dwijnand
Jun 28 2016 00:46
then rewire the run in the aggregate project to the one in the subproject
Dale Wijnand
@dwijnand
Jun 28 2016 00:50
that's it
Jonathan Ferguson
@jonoabroad
Jun 28 2016 00:52
thank you.
Dale Wijnand
@dwijnand
Jun 28 2016 00:53
np
Stefan Larsson
@lastsys
Jun 28 2016 06:01
@nafg Sure. I have never bothered myself.
Marek ┼╗ebrowski
@marekzebrowski
Jun 28 2016 10:09

Hello, is it possible to publish sbt plugin to sonatype repository? I'm trying to do it using settings:

sbtPlugin    := true
publishMavenStyle := true

but operation fails with:
[error] (*:publish) java.io.IOException: PUT operation to URL https://nexus.groupl.es/repository/maven-releases/me/sgrouples/solr-plugin_2.10_0.13/1.0.0/solr-plugin-1.0.0.pom failed with status code 400: Invalid path for a Maven 2 repository

Konstantin Kirillov
@ostronom
Jun 28 2016 12:16

Hello. I have a strange problem with "illegal dynamic reference" in my sbt plugin (https://github.com/ostronom/sbt-native-packager/blob/issue-723/src/main/scala/com/typesafe/sbt/packager/archetypes/JavaExternalDeps.scala#L78). This line produces two illegal dynamic reference errors -- one for each use of ref.

There was a discussion on github (sbt/sbt-native-packager#723) in which sbt-native-packager author suggested me to use Def.settingDyn to solve this. But neither he nor me were able to figure out how exactly this can be accomplished.

So, I'm asking it here. I've tried to use Def.taskDyn (as settingDyn cannot be used here, because settings cannot depend on tasks), but I am getting the same failure anyway.

How do I avoid/workaround/solve this?

Konstantin Kirillov
@ostronom
Jun 28 2016 12:26
Yes, i did read it
But any time I address SettingKey in ref's value I'm getting this error
Perry
@pfn
Jun 28 2016 15:27
scriptClasspath := Def.taskDyn {
  ...
  Def.task {
    blah.value flatMap { ref =>
      .... (javaLibraryPath in ref).value ....
    }
  }
}
@ostronom
should work fine
nafg
@nafg
Jun 28 2016 16:12
anyone have some wisdom on keeping projects with lots of modules (sbt subprojects) sane?
Here's a mostly up to date dependency graph:
This message was deleted
graph.png
Now I started doing scala-js, so I have js-client
And then I need to be able to share code between the server and js
so I guess that means another (double) module?
And at what granularity level?
I don't want to put too much into a single scalajs project because it increases the js file size
but I don't want to put too little because then the number of modules will really get out of hand
but at what at granularity should the shared code be?
nafg
@nafg
Jun 28 2016 16:25
actually I realized my dependencies were a bit simplistic
let me update
graph.png