sbt/sbt

A relaxed chat room about sbt (That interactive build tool). For getting help on sbt, we encourage people to document it on Stackoverflow or subscribing to Lightbend subscription.

Jorge

@jvican

Gitter is not the great medium to discuss this, lots of people are missing out :P

Jose C

@jmcardon

Oh definitely, I just wanted to give some background on gitter for the ones already here :P

Jorge

@jvican

thanks :)

Jose C

@jmcardon

I'll come back to the discussion when it's developed a bit more

No problem

Sukant Hajra

@shajra

I just noticed a lot of people putting the same version they put in scalaVersion also in crossScalaVersions. But it just occurred to me that it might be convenient to have them as disjoint sets? But I can't exactly put it to words. It seems kind of annoying when building everything to have to write ; command ; + command

I think there's not a right/wrong answer... just curious if people have already thought about it.

eugene yokota

@eed3si9n

the logical end of that line is sbt-doge

s3ni0r

@s3ni0r

Hi everyone, i have a custom resolver in my build.sbt file that's not challenged when resolving dependecies :

[warn]     ::::::::::::::::::::::::::::::::::::::::::::::
[warn]     ::          UNRESOLVED DEPENDENCIES         ::
[warn]     ::::::::::::::::::::::::::::::::::::::::::::::
[warn]     :: com.spingo#op-rabbit-core_2.11;1.2.1: not found
[warn]     ::::::::::::::::::::::::::::::::::::::::::::::
[warn] 
[warn]     Note: Unresolved dependencies path:
[warn]         com.spingo:op-rabbit-core_2.11:1.2.1 (/builds/root/xxxxx/build.sbt#L115)
[warn]           +- xxxxxx-commons:xxxxxx-commons_2.11:1.0
[info] 'compiler-interface' not yet compiled for Scala 2.11.7. Compiling...
[info]   Compilation completed in 8.421 s
sbt.ResolveException: unresolved dependency: com.spingo#op-rabbit-core_2.11;1.2.1: not found
    at sbt.IvyActions$.sbt$IvyActions$$resolve(IvyActions.scala:291)
    at sbt.IvyActions$$anonfun$updateEither$1.apply(IvyActions.scala:188)
    at sbt.IvyActions$$anonfun$updateEither$1.apply(IvyActions.scala:165)
    at sbt.IvySbt$Module$$anonfun$withModule$1.apply(Ivy.scala:155)
    at sbt.IvySbt$Module$$anonfun$withModule$1.apply(Ivy.scala:155)
    at sbt.IvySbt$$anonfun$withIvy$1.apply(Ivy.scala:132)
    at sbt.IvySbt.sbt$IvySbt$$action$1(Ivy.scala:57)
    at sbt.IvySbt$$anon$4.call(Ivy.scala:65)
    at xsbt.boot.Locks$GlobalLock.withChannel$1(Locks.scala:93)
    at xsbt.boot.Locks$GlobalLock.xsbt$boot$Locks$GlobalLock$$withChannelRetries$1(Locks.scala:78)
    at xsbt.boot.Locks$GlobalLock$$anonfun$withFileLock$1.apply(Locks.scala:97)
    at xsbt.boot.Using$.withResource(Using.scala:10)
    at xsbt.boot.Using$.apply(Using.scala:9)
    at xsbt.boot.Locks$GlobalLock.ignoringDeadlockAvoided(Locks.scala:58)
    at xsbt.boot.Locks$GlobalLock.withLock(Locks.scala:48)
    at xsbt.boot.Locks$.apply0(Locks.scala:31)
    at xsbt.boot.Locks$.apply(Locks.scala:28)
    at sbt.IvySbt.withDefaultLogger(Ivy.scala:65)
    at sbt.IvySbt.withIvy(Ivy.scala:127)
    at sbt.IvySbt.withIvy(Ivy.scala:124)
    at sbt.IvySbt$Module.withModule(Ivy.scala:155)
    at sbt.IvyActions$.updateEither(IvyActions.scala:165)
    at sbt.Classpaths$$anonfun$sbt$Classpaths$$work$1$1.apply(Defaults.scala:1369)
    at sbt.Classpaths$$anonfun$sbt$Classpaths$$work$1$1.apply(Defaults.scala:1365)
    at sbt.Classpaths$$anonfun$doWork$1$1$$anonfun$87.apply(Defaults.scala:1399)
    at sbt.Classpaths$$anonfun$doWork$1$1$$anonfun$87.apply(Defaults.scala:1397)
    at sbt.Tracked$$anonfun$lastOutput$1.apply(Tracked.scala:37)
    at sbt.Classpaths$$anonfun$doWork$1$1.apply(Defaults.scala:1402)
    at sbt.Classpaths$$anonfun$doWork$1$1.apply(Defaults.scala:1396)
    at sbt.Tracked$$anonfun$inputChanged$1.apply(Tracked.scala:60)
    at sbt.Classpaths$.cachedUpdate(Defaults.scala:1419)
    at sbt.Classpaths$$anonfun$updateTask$1.apply(Defaults.scala:1348)
    at sbt.Classpaths$$anonfun$updateTask$1.apply(Defaults.scala:1310)
    at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
    at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
    at sbt.std.Transform$$anon$4.work(System.scala:63)
    at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
    at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
    at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
    at sbt.Execute.work(Execute.scala:235)
    at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
    at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
    at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159)
    at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
[error] (crawlerCommons/*:update) sbt.ResolveException: unresolved dependency: com.spingo#op-rabbit-core_2.11;1.2.1: not found

i can't figure out why this is happening

these are my resolvers :

resolvers ++= Seq(
      Resolver.sonatypeRepo("snapshots")
      ,Resolver.sonatypeRepo("releases")
      ,Resolver.typesafeRepo("releases")
      ,"spray repo" at "http://repo.spray.io"
      ,"SpinGo OSS" at "http://spingo-oss.s3.amazonaws.com/repositories/releases"
    )

and this what i got as warning messages that confirms the issue :

[info] Resolving com.spingo#op-rabbit-core_2.11;1.2.1 ...
[warn]     module not found: com.spingo#op-rabbit-core_2.11;1.2.1
[warn] ==== local: tried
[warn]   /root/.ivy2/local/com.spingo/op-rabbit-core_2.11/1.2.1/ivys/ivy.xml
[warn] ==== local-preloaded-ivy: tried
[warn]   /root/.sbt/preloaded/com.spingo/op-rabbit-core_2.11/1.2.1/ivys/ivy.xml
[warn] ==== local-preloaded: tried
[warn]   file:////root/.sbt/preloaded/com/spingo/op-rabbit-core_2.11/1.2.1/op-rabbit-core_2.11-1.2.1.pom
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/com/spingo/op-rabbit-core_2.11/1.2.1/op-rabbit-core_2.11-1.2.1.pom

Ghost

@ghost~540393fe163965c9bc2018ce

omg I wish for parallel scripted so much :cry:

Dale Wijnand

@dwijnand

sbt 1 scripted has improved, though I didn't review how.

Jorge

@jvican

sbt 1's scripted is parallel

and allows batch test execution

Dale Wijnand

@dwijnand

"Add parallel batch mode to scripted tests" sbt/sbt#3151

Jorge

@jvican

(one scripted instance can run several scripted tests)

Dale Wijnand

@dwijnand

Sam how much do you want sbt 1 to be released?

Jorge

@jvican

by the way folks, i have released a plugin you may be interested in: https://github.com/scalacenter/sbt-release-early

allows you to release on merge and via git tags + niceties to make releasing easier

good docs too (i hope)

Ghost

@ghost~540393fe163965c9bc2018ce

I've already got that all automated, thanks

the reason I don't do final release on merge is because I wouldn't put by GPG key on anything other than my personal computer

Jorge

@jvican

i don't use my personal GPG key

also, with drone releases should be more secure

https://github.com/scalacenter/sbt-release-early#secure-releases

Ghost

@ghost~540393fe163965c9bc2018ce

that's pretty sad that people are not putting passphrases on their GPG keys... I predict this will bite us one day

that said, it's not like anybody is checking the binaries.

Jorge

@jvican

have a look at that section, there i argue what it's required for a "secure" release process, where secure means "secure enough"

Ghost

@ghost~540393fe163965c9bc2018ce

and sonatype have basically zero security process

Jorge

@jvican

oh, i'm using passphrases for my CI gpg key :)

yeah, i wish there was an easier/better way for this

i've thought a lot about it, too

Ghost

@ghost~540393fe163965c9bc2018ce

it's not much better in other languages either... this will be the future of a high profile crack one day.

Sukant Hajra

@shajra

@eed3si9n when using sbt-doge, do you respecify the value for scalaVersion in crossScalaVersions?

Or is there a way of using sbt-doge that makes this practice unnecessary?

scalasolist

@scalasolist

What is the supposed way to pass JVM options to the sbt command?

eugene yokota

@eed3si9n

it depends. i think you would always want to have scalaVersion to some value so you can run tests without cross building. doge helps when you have heterogenous build with varying crossScalaVersions

Ghost

@ghost~540393fe163965c9bc2018ce

@scalasolist to sbt itself, use .jvmopts one line per arg, for launched processes you need to use fork := true and then use javaOptions ++= Seq(...)

eugene yokota

@eed3si9n

sbt commands normally inherits the jvm that sbt itself is running under

and what sam said

scalasolist

@scalasolist

@fommil thanks. .jvmopts is what I'm searching

Ghost

@ghost~540393fe163965c9bc2018ce

it even works on windows ;-)

Sukant Hajra

@shajra

@eed3si9n okay for the company, I have a small function that takes (mainTarget: ScalaTarget, others: ScalaTargets*) and it sets scalaVersion to just mainTarget, and crossScalaVersions to mainTarget +: others.

scalasolist

@scalasolist

where should I put .jvmopts?

Ghost

@ghost~540393fe163965c9bc2018ce

just in the root of your project

I also recommend using jenv to manage your version of java, and put a .java-version file beside the .jvmopts

eugene yokota

@eed3si9n

+1 on jenv

scalasolist

@scalasolist

eselect java-vm is sufficient for me

Where communities thrive

People

Repo info

Activity