-
Notifications
You must be signed in to change notification settings - Fork 59
add sbt 1.0 and zinc (as a project in the build) #581
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
Conversation
results from local testing of this first stab:
I imagine the issue is that sbt 1.0 is now built with sbt 1.0, but the community build is still on 0.13.16. so I guess #552 is a prerequisite for this |
configs/project-refs.conf
Outdated
sbt-uri: "https://github.com/sbt/sbt.git#1.0.0" | ||
sbt-io-uri: "https://github.com/sbt/io.git#v1.0.0-M11" | ||
sbt-librarymanagement-uri: "https://github.com/sbt/librarymanagement.git#v1.0.0-X15" | ||
sbt-util-uri: "https://github.com/sbt/util.git#v1.0.0-M24" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Seth, after the unrelated breakage in lightbend-labs/mima#191 I was thinking about how our cross-repo source/binary breakages in sbt are over so we should get our code building with everything else. (and then I forgot to do anything about it)
The possible targets for compilation are either:
- the latest tags (RC3 across the board, rather than the misc X??/M?? tags)
- the temporary 1.0.0 release branches, where the latest RC fixes are being merged, in prep for the v1.0.0 releases, then will be merged into 1.x and deleted
- the 1.x branches
Personally I'd track 1.0.0, and then switch when we delete them - I'll try and remember to PR or at least ping you.
WRT dbuild, work is progressing I see in lightbend-labs/dbuild#198, but @cunei's on a well deserved break atm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is blocked on sbt 1.0 support in dbuild, so considering it on hold for now.
but, I will separately try to add zinc, just by itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SethTisue dbuild 0.9.9 is out, with support for sbt 1.0.0 final.
never mind about adding zinc separately, it depends on sbt modules, so this will all need to happen together |
dbuild bump is #585 |
@dwijnand what do you make of this?
|
Yoshida-san has already fixed it in thesamet/sbt-protoc#33 and it just got released. So I'll finish upgrading zinc's build in sbt/zinc#385 and once merged this should unblock. |
cc1b4aa
to
583c968
Compare
I made some very good progress on this today:
|
but as seen at https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1782/consoleFull I am currently getting:
@dwijnand @eed3si9n @jvican any insight into what's going on here? |
(I can work around it by just not running the zinc tests, but of course it would be better if we could run them) |
Deviating from the norm, zinc's tests require things to be locally published, so they can be retrieved while testing. This trips up dbuild, so that test won't pass. I think we should look at ways to make those tests opt-out-able (test tags or something?) so we can run our suite against the nightly compilers. |
fixes #264