-
Notifications
You must be signed in to change notification settings - Fork 65
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
sbt-sonatype 3.9.7 does not work with sbt 1.3.x #91
Comments
ok. I'll rollback to sbt 1.2.8 and release a new build for now. |
Just released sbt-sonatype 3.2 for sbt 1.2.8 |
I've confirmed sbt-sonatpye 3.2 can be used both for sbt 1.2.8 and 1.3.0. |
@xerial The same happens now with 3.9.7 because you upgraded to sbt 1.4.9 in 3b62104 Can you rollback to 1.2.8? Also because that happens from minor release 3.9.6 to 3.9.7... |
@mkurz I had trouble in using sbt 1.2.x probably because of the sunset of Bintray. My counter question would be what is blocking you from using sbt 1.4.x or higher, which already has no such an issue. A workaround might be releasing sbt-sonatype against sbt-1.1.x series by changing this line: Line 32 in 33b6ea4
|
Changed the ticket title and reopened the issue. A preferred direction for me is dropping the support for old sbt versions (e.g., 1.2.8) and encourage everybody to migrate to sbt 1.4.x or later. One of the reasons is the old sbt binaries may not be available after bintray is totally shutdown. Another reason is I couldn't compile sbt-sonatype in a new machine, which has no sbt binary in the local cache, if we stick to 1.2.8. |
I think dropping 1.2.x is pretty much a no-brainer at this point. Dropping 1.3.x too would be a bit bolder move, but seems quite reasonable to me. (And I don't think you should worry about the Bintray thing — both Lightbend and the Scala Center are working on preserving the archives. I can't 100% promise an ideal outcome til it happens, but I suggest optimism here rather than pessimism.) |
We are now in sbt 1.6.x. I believe it's safe to drop support for |
Maybe sbt 1.2.8 to 1.3.0 break forward binary compatibility? 😢
Should use sbt 1.2.8 when plugin build (if support sbt 1.2)? or await release sbt 1.3.1? /cc @eed3si9n
The text was updated successfully, but these errors were encountered: