Add sbt-vspp for publishing the BLOOP SBT plug-in in a Maven-consistent format #1766
Conversation
This is to enable usage of Bloop/Metals in Enterprise environments where only the valid-POM format is accepted for JAR downloads (meaning most SBT plug-ins don't work -- currently making Scala unusable from VS Code at organizations with stricter security policies), for thousands of developers. -- How this is tested locally: `publishM2`, then in the target project that uses sbt-bloop, in its `project/metals.sbt` add, e.g.: ``` libraryDependencies += "ch.epfl.scala" % "sbt-bloop_2.12_1.0" % "1.5.2-13-15ded987-20220726-1436" // only needed if published to local .m2 via publishM2 resolvers += Resolver.mavenLocal ```
|
@ScalaWilliam Thanks for the contribution! I went trough all attached info and original issue in sbt - didn't know about this issue 😅 |
Yeah, I am kind of curious what it's not being done by default 🤔 I am totally ok with merging, just I am surprised it's not being handled properly in the first place. |
|
@adpi2 Could you take a look at this? Is there any chance that it will be ported to sbt? |
|
Let's merge it an see if it works correctly in Metals. |
3 participants
This is to enable usage of Bloop/Metals in Enterprise environments where only the valid-POM format is accepted for JAR downloads (meaning most SBT plug-ins don't work -- currently making Scala unusable from VS Code at organizations with stricter security policies), for thousands of developers.
--
How this is tested locally:
publishM2, then in the target project that uses sbt-bloop, in itsproject/metals.sbtadd, e.g.:More background here - https://github.com/esbeetee/sbt-vspp - more than happy to hop on a video call to discuss - as I appreciate that this is a non-issue for those that have a direct connection to Maven Central.