Unresolved dependency in spray when building locally about community-build HOT 5 CLOSED

That's a dependency of the build itself. You may want to add the spray repo resolver to get it:

resolvers += "spray repo" at "http://repo.spray.io"

I don't know why dbuild isn't picking it up itself and why it works for the jenkins build.

from community-build.

Ah but where can I put this config line? The only candidate that came to my mind was -- very ugly -- ./sbt/0.13/plugins/something.sbt, but that didn't help.

from community-build.

I don't really know, but the documentation of dbuild says:

-l, --local                  Equivalent to: --no-resolvers --no-notify
-r, --no-resolvers           Disable the parsing of the "options.resolvers"
                               section from the dbuild configuration file: only
                               use the resolvers defined in dbuild.properties

So, I guess the dbuild.properties file would be the place to add it (wherever that lives).

from community-build.

OK, I managed to get it working by adding the following line

repo-spray: http://repo.spray.io

under [repositories] in <community-build>/dbuild-0.9.1/bin/dbuild.properties.

from community-build.

closing on the assumption that lots has changed since the initial report. we can reopen if it rears its head again.

running the full community build locally is generally not recommended since it takes forever because you won't benefit from the caching the real Jenkins jobs on scala-ci have. if you have a branch with changes to the community build config you want to test, let us know, we can run them on Jenkins for you.

from community-build.