-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade to newer dbuild 0.9.3+ #108
Comments
I would recommend 0.9.3-M3; despite the "M3", it should be fully stable. |
@cunei are there release notes for 0.9.2 and 0.9.3-M3? |
@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 |
0.9.3 is out (release notes) |
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 |
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.) |
actually running locally works fine as long as you run with regardless, we should be on the latest dbuild, if only to help dogfood it for RP |
0.9.4 is out and includes a better default repo list. |
once #185 is fixed, we'll be free to upgrade to 0.9.4 afaict |
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) |
this is not pressing, but presumably we should upgrade eventually
a previous attempt to upgrade from 0.9.1 to 0.9.2 went awry; gory details at scala-ide/uber-build#64 . as of June 2015, there is no 0.9.3 release
The text was updated successfully, but these errors were encountered: