Metals: Publish lsp4s for scala 2.11

Created on 6 Feb 2018  ·  10Comments  ·  Source: scalameta/metals

I'm using and enjoying lsp4s, but as I am currently stuck on 2.11 I have copied and pasted it into my local project and would prefer to just use a published version compatible with 2.11

build

Most helpful comment

lsp4s is now released for 2.11

coursier fetch org.scalameta:lsp4s_2.11:6f55b052 -r bintray:scalameta/maven

Note that we have not tested it for 2.11, only 2.12. See #191

All 10 comments

Good idea! I don't think we use any 2.12-only features in lsp4s. Cross-building should be a matter of updating crossScalaVersions to include 2.11 and make sure sbt releaseEarly handles cross-versions.

I don't think we use any 2.12-only features in lsp4s

Almost 😛 Remember when I pushed you to use a lot of SAMs?

See #190

Fixed in #190 , CI should release to Bintray once tests complete after merge @ShaneDelmore

I'm having no luck with this. Am I doing something wrong?
In sbt I have added

scalaVersion := "2.11.12"
resolvers += Resolver.bintrayRepo("scalameta", "maven")

but still neither of these work:

libraryDependencies ++= List(
"org.scalameta" %% "lsp4s" % "325610ac",
"org.scalameta" %% "jsonrpc" % "325610ac"
)

I don't think the CI is configured to release for 2.11, 2.12 downloads OK

 coursier fetch org.scalameta:lsp4s_2.12:68015934 -r bintray:scalameta/maven

https://bintray.com/scalameta/maven/lsp4s/68015934

Can you check the .travis.yml?

It's probably a missing + in front of releaseEarly

--
Gabriele

On 9 Feb 2018, 00:41 +0100, Ólafur Páll Geirsson notifications@github.com, wrote:

I don't think the CI is configured to release for 2.11, 2.12 downloads OK
coursier fetch org.scalameta:lsp4s_2.12:68015934 -r bintray:scalameta/maven
https://bintray.com/scalameta/maven/lsp4s/68015934
Can you check the .travis.yml?

You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

+ won't work because metaserver is 2.12 only, @laughedelic any idea how to such publish sbt-doge style?

+ probably works actually because we are using sbt 1.0 where sbt-doge is no longer needed 🙏

let's check if it works now https://travis-ci.org/scalameta/metals/builds/339421516

lsp4s is now released for 2.11

coursier fetch org.scalameta:lsp4s_2.11:6f55b052 -r bintray:scalameta/maven

Note that we have not tested it for 2.11, only 2.12. See #191

@olafurpg sorry, I couldn't reply before. But yes, you are right, sbt-doge got "merged" into sbt 1.0, so + should work for relevant subprojects without extra effort.

Was this page helpful?
0 / 5 - 0 ratings