exclude default resolver repos

253 views
Skip to first unread message

Sam Halliday

unread,
Jun 12, 2015, 5:09:19 AM6/12/15
to sbt...@googlegroups.com
Hi all,

I'm using sbt behind a corporate firewall and I've overridden the default resolvers in three locations:

1. in the Build.scala

    resolvers := Seq(
      "default" at "..."
    )

2. in the .jvmopts 

-Xss2m
-Xmx8g
-XX:+UseConcMarkSweepGC
-Dsbt.repository.config=.sbt-repositories

[repositories]
local
my-ivy-proxy-releases: http://MY_MIRROR/nexus/content/groups/mirror/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext]


3. in the .sbtopts (this might only be relevant for paulp's launch script)

-java-home
/opt/jenkins/jdk1.8.0_40
-sbt-launch-repo


But when I start up sbt with a plugin like sbt-native-packager in my plugins.sbt list, sbt is *still* trying to go to the outside world to resolve the dependency:




What else do I need to do to tell sbt not to use the baked-in resolver lists?

Best regards,
Sam

Sam Halliday

unread,
Jun 12, 2015, 5:23:27 AM6/12/15
to sbt...@googlegroups.com
Doh! I forgot the

  -Dsbt.override.build.repos=true

in the .jvmopts.

Joshua Suereth

unread,
Jun 12, 2015, 9:01:34 AM6/12/15
to sbt-dev

Override build repos should be all that's required (beyond having the repositories file configured correctly).  That has to be passed to the sbt launcher, and sbt version must be 0.13+

Can you clarify if the relative .sbtrrpositories flag is working correctly for you?

--
You received this message because you are subscribed to the Google Groups "sbt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sbt-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sbt-dev/50632223-e31d-4a51-8358-ffa9c94fdf0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sam Halliday

unread,
Jun 12, 2015, 9:46:40 AM6/12/15
to sbt...@googlegroups.com
This wasn't so much about not using my internal resolvers, as excluding the default ones. Adding the extra java flag seems to have fixed it.
Reply all
Reply to author
Forward
0 new messages