Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 10 09:15
    scala-steward closed #229
  • May 10 09:15
    scala-steward opened #233
  • May 02 11:14
    mergify[bot] closed #232
  • May 02 11:05
    scala-steward opened #232
  • Apr 30 07:47
    rtimush closed #231
  • Apr 29 21:33
    dependabot-preview[bot] labeled #231
  • Apr 29 21:33
    dependabot-preview[bot] opened #231
  • Apr 26 21:19
    rtimush synchronize #229
  • Apr 26 21:17
    mergify[bot] closed #230
  • Apr 26 20:43
    rtimush synchronize #230
  • Apr 26 20:39
    scala-steward closed #228
  • Apr 26 20:39
    scala-steward opened #230
  • Apr 26 13:16
    scala-steward opened #229
  • Apr 21 00:18
    scala-steward opened #228
  • Apr 20 20:55
    mergify[bot] closed #227
  • Apr 20 20:45
    scala-steward opened #227
  • Apr 12 13:27
    rtimush closed #226
  • Apr 12 13:03
    travisbrown opened #226
  • Apr 05 14:17
    rtimush closed #225
  • Apr 05 14:08
    rtimush auto_merge_enabled #225
Danila Matveev
@optician
Hi!
Met a problem with sbt 1.0.0-RC3. It tries to search plugin in /scala_2.12/sbt_1.0//0.3.1/ but artifacts are in /scala_2.12/sbt_1.0.0-M6/0.3.1/
Roman Timushev
@rtimush
Hi. The latest release wasn’t built for sbt 1.0.0-RC3 yet, but you can try the latest snapshot.
0.3.2-1+g3280e1e
You will also need to add resolvers += Resolver.url("rtimush/sbt-plugin-snapshots", new URL("https://dl.bintray.com/rtimush/sbt-plugin-snapshots/"))(Resolver.ivyStylePatterns)
Danila Matveev
@optician
It works. Thx!
Roman Timushev
@rtimush
Welcome!
Roman Timushev
@rtimush
0.3.1 should now work with sbt 1.0.0-RC3 as well
Danila Matveev
@optician
Thx again!
Stephen Duncan Jr
@jrduncans

Tried out the plugin a few days ago and it worked, but now I'm getting:

[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: com.timushev.sbt#sbt-updates;0.3.4: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn] Note: Some unresolved dependencies have extra attributes. Check that these dependencies exist with the requested attributes.
[warn] com.timushev.sbt:sbt-updates:0.3.4 (scalaVersion=2.12, sbtVersion=0.13)

Roman Timushev
@rtimush
Hi @jrduncans. Looks like something wrong with your project setup — the error says SBT 0.13 & Scala 2.12, but SBT 0.13 uses 2.10
Stephen Duncan Jr
@jrduncans
Hmm. I do see it working on another project. This is when I have it as a global setting in ~/.sbt/0.13/global.sbt, strangely when I comment that out and it to the same project in project/plugins.sbt it works. Not sure what would cause that, but I guess if I want that answer I'll take it over to the sbt channel...
Oh, I guess I should have put it in ~/.sbt/0.13/plugins/plugins.sbt ... Sorry for the noise.
Roman Timushev
@rtimush
Yes, ~/.sbt/0.13/plugins/plugins.sbt is the right place. No worries, have fun with sbt-updates :)
Dennis Mellert
@herzrasen
Hi, I'm unable to get dependencyUpdates on Linux. It always returns: [info] No dependency updates found for xxx. I tried multiple distributions but without any success. I'm inside a company network with a company internal CA which I added to the Java keystore. Any idea what I can do to get this working?
Dennis Mellert
@herzrasen
@herzrasen nevermind, it was due to a missing .ivy2/.credentials file.
Thomas Heslin
@tjheslin1
Hi. I’m running sbt-updates on a project and noticed that it’s not recommending updating "io.cucumber" %% "cucumber-scala" % “2.0.1" % "e2e”, where the latest version is 4.2.0
Will it not suggest such a major upgrade?
Thomas Heslin
@tjheslin1
I realised that this was due to a dependencyUpdatesFilter on org.apache.spark", revision = “2.3.2"
Harpreet Singh
@harpresing

I was just wondering if sbt-updates works with private repositories hosting the artifacts?

For instance in my .sbtopts I have the options -Dsbt.override.build.repos=true and -Dsbt.repository.config=project/repositories/<my-private-repo>, with these options when I run sbt dependencyUpdates I get No dependency updates found for <project>.

However when I remove those sbt options and use the default scala repositories, running sbt dependencyUpdates prints out a lot of dependencies which have newer versions.

Is this the expected behaviour?

Thanks!

Roman Timushev
@rtimush
Hi @etSingh. In general, sbt-updates should work for private repositories in the same way as it works for the public ones. If you run set -debug dependencyUpdates you will see which metadata files it downloads to get the list of versions. Do you know which technology is powering the private repository you use?