upgrade to newer dbuild 0.9.3+ about community-build HOT 10 CLOSED

I would recommend 0.9.3-M3; despite the "M3", it should be fully stable.

from community-build.

@cunei are there release notes for 0.9.2 and 0.9.3-M3?

from community-build.

@SethTisue Not as such; there is of course the commit log. The updated documentation pages are at https://github.com/typesafehub/dbuild/tree/v0.9.3-M3/docs/src/sphinx
At this point I could promote 0.9.3-M3 to 0.9.3-final, publish dbuild, update the website, and collect the release notes. Friday is a holiday in the US, but not in Switzerland: I should be able to take care of this matter then. @jsuereth

from community-build.

0.9.3 is out (release notes)

from community-build.

I tried 0.9.3 but it fails because of lightbend/config#160. /cc @cunei

I'm not sure, but it looks like the config should be accepted, and the error message for lightbend/config#160 is a bit overzealous. We need this construct to work around lightbend-labs/dbuild#144

from community-build.

another reason to upgrade is to get the fix for lightbend-labs/dbuild#175, except we'd actually need 0.9.4 published in order to get that fix, since it came after 0.9.3

that issue prevents dbuild from working at all locally, since sbt plugins can't be found. (I suspect it only works on Jenkins because the plugin artifacts are in the artifact cache we use there.)

from community-build.

actually running locally works fine as long as you run with -n instead of -l

regardless, we should be on the latest dbuild, if only to help dogfood it for RP

from community-build.

0.9.4 is out and includes a better default repo list.

from community-build.

once #185 is fixed, we'll be free to upgrade to 0.9.4 afaict

from community-build.

fixed for 2.11.x-jdk8 (and 2.12, once I merge it forward) by #189 . I don't think it's necessary to mess with 2.11.x(-jdk6)

from community-build.