-
Notifications
You must be signed in to change notification settings - Fork 113
sbt 1.0 release #134
Comments
Yes, definitely, there will be a release for sbt 1.0. Just didn't get to it
due to summer outside :)
|
Summer outside? Not in Germany right now ;-) |
I had a look at sbt 1.0 support at the weekend. It's far from trivial:
I'm treating this with some priority but depending on the amount of work it might still take a while. If someone wants to help just taking the existing code and fixing the deprecations against sbt 0.13 would help a lot. |
I managed to do these mostly yesterday evening. Someone also pointed to an old branch at https://github.com/jrudolph/sbt-dependency-graph/tree/w/sbt-1.0.0-M4-support I had forgotten about that could help with the first bullet point. |
sbt 1.0.1 is there :) |
Unfortunately, it hasn't fixed bugs like sbt/sbt#3299. Anyway I have published a 0.8.3-SNAPSHOT version to sonatype for the brave ones. |
Thanks for publishing the snapshot. I've given it a go on a fairly large project (~ 150 deps) without any issue. |
Is sbt/sbt#3299 a show-stopping bug? |
With regards to cross-building please note that https://github.com/dwijnand/sbt-compat is available, and I'm happy to accept changes for any shim required by sbt-dependency-graph. |
@dwijnand sbt/sbt#3299 was closed 7 days ago. Oops, it was You who closed it. O:) |
0.8.3-SNAPSHOT is working well for me |
Seems like people are having good luck with the snapshot, and the prereq issues are fixed: Is it time to release 0.8.3 (or 0.9)? |
As part of SCP-013 the Scala Center has the task to help the community migrate their plugins. Since this plugin is on the top of the sbt 1.0 migration list we are offering our help. Here is my plan:
|
Just completed the first phase: #139 |
@MasseGuillaume sorry for not answering any sooner here. Have you seen #137 and #138? This contains the current state of the migration. I think the simple things have mostly been solved and I published a SNAPSHOT of sbt 1.0 support a while ago from that branch. However, I'd like to be able to keep cross-building to sbt 0.13. So, basically what's missing is taking #137/#138 and make sure that they can be cross-built against 0.13. |
Yep I saw both branches. I took a bit of your work in #137 I can add you as an author in the commit message if you want. |
Wow that was fast. Thanks a lot. I'll take it for a spin later on 👍
Am 17.10.2017 8:57 vorm. schrieb "Guillaume Massé" <[email protected]
…:
@jrudolph <https://github.com/jrudolph>
sbt-dependency-graph is now cross compiled between sbt 1.0 and 0.13
You need to merge #139
<#139> then #140
<#140>. Then you can
publish with sbt "^ publish". Let me know If I missed anything.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#134 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAmjEKi_5rX4QGfCvCK3SDP8AB_aMQJks5stLJggaJpZM4O0bqe>
.
|
Is there anything the community can do to help get this released? |
I just merged all the pending PRs for the 1.0 upgrade and released 0.9.0 for both sbt 0.13 and 1.0. Thanks a lot again, @MasseGuillaume and Scala Center for helping out to get this finally resolved. |
Thanks a bunch!!! |
Is there a plan to release an sbt 1.0 compatible plugin? #132 is related.
I had a quick look regarding the sbt-dependency-graph build and found that sbt-pgp 1.1.0-M1 supports sbt 1.0. I raised sbt/sbt-scalariform#64. There seems to be more required for the sbt scripted-plugin than just uptaking org.scala-sbt#scripted-plugin_2.12;1.0.0.
I've tried the sbt-coursier plugin and it does work but it doesn't have the same features as this plugin.
The text was updated successfully, but these errors were encountered: