These are chat archives for sbt/sbt

11th
Jan 2017
Todd Leo
@toddleo
Jan 11 02:10
anyone knows what would affect the version in myname-0.1.jarwhen building it?
marios iliofotou
@imarios
Jan 11 02:10
the version setting?
e.g., version := "1.0"
Todd Leo
@toddleo
Jan 11 02:15
i have set the version to 1.0, except the target jar name is still ...-0.1.jar
marios iliofotou
@imarios
Jan 11 02:16
maybe you defined it in a different scope? Is this a multi-project build?
Todd Leo
@toddleo
Jan 11 02:17
no it is not
marios iliofotou
@imarios
Jan 11 02:17
version in Global := "1.0" works?
Todd Leo
@toddleo
Jan 11 02:20
wait I'm trying
do I use sbt package or what? :smile:
marios iliofotou
@imarios
Jan 11 02:29
do you have a project ? (defined using project.in(file("something")))
Todd Leo
@toddleo
Jan 11 02:29
no it just goes:
name := "jarvis"
//version := "1.1.2"
version in Global := "1.0"

libraryDependencies += ...
marios iliofotou
@imarios
Jan 11 02:30
so doing sbt package still gives you "0.1"?
Todd Leo
@toddleo
Jan 11 02:31
Ahhhhh I found the reason I somehow put another version := 0.1 at the bottom
sorry for that
marios iliofotou
@imarios
Jan 11 02:32
=)
You don't need the global, just have one version and you are good
Todd Leo
@toddleo
Jan 11 02:38
I guess so until I need to split it into multi project
:smile:
Mirco Dotta
@dotta
Jan 11 16:50
I’ve implemented a custom (sbt) compiler-bridge but projects are failing to resolve it. I’ve read https://github.com/sbt/sbt/commit/6c1b0542494b770a95fe3a77415a630dce5fb5ae#diff-298b9822bdc6e41b74d9fe9556ed17d6R17, but I’m failing to understand what "The source module will be retrieved using library management configured by bootIvyConfiguration task.” means in practice. Basically, I’m wondering how do I specify the resolver for my custom compiler-bridge, or is there more I’d have to do?
Mirco Dotta
@dotta
Jan 11 17:25
Alright, I’ve managed to make it work by creating a method identical to https://github.com/sbt/sbt/blob/274c8ec65f75415dd382c642f50368c53752515d/main/src/main/scala/sbt/Defaults.scala#L1852-L1859, but that declares the resolver where my custom compiler-bridge is deployed. Then I simply added bootIvyConfiguration := mkIvyConfiguration.value in the build, and it worked. Would be great if someone could confirm this is the correct way to do it.
marios iliofotou
@imarios
Jan 11 19:46
Anyone ever experience publish (tried with publishM2) to package the same test code for all three (-sources.jar, -tests.jar, and regular jar)?
so all those three have the same code and is only the test code (including the resources under test)