From 96d47e80f4fcc6b9e200e98207bae517b814eb15 Mon Sep 17 00:00:00 2001
From: ScalaWilliam <hello@scalawilliam.com>
Date: Thu, 28 Jul 2022 21:27:45 +0100
Subject: [PATCH] Add sbt-vspp for publishing the SBT plug-in in a
 Maven-consistent format

This is to enable usage of sbt-scoverage in Enterprise environments where only the valid-POM format is accepted for JAR downloads, enabling it for many teams to move from Gradle/Maven to SBT for their Scala (and even non-Scala projects)

More background here: https://github.com/esbeetee/sbt-vspp/blob/main/README.md
---
 README.md           | 5 +++++
 project/plugins.sbt | 1 +
 2 files changed, 6 insertions(+)

diff --git a/README.md b/README.md
index 7a14dad3..c279783d 100644
--- a/README.md
+++ b/README.md
@@ -19,6 +19,11 @@ In `project/plugins.sbt`:
 addSbtPlugin("org.scoverage" % "sbt-scoverage" % "x.x.x")
 ```
 
+If you are in an enterprise environment, and the above does not work, try:
+```scala
+libraryDependencies += "org.scoverage" % "sbt-scoverage_2.12_1.0" % "x.x.x"
+```
+
 ## Usage
 
 Run the tests with enabled coverage:
diff --git a/project/plugins.sbt b/project/plugins.sbt
index 19695c2e..7f164332 100644
--- a/project/plugins.sbt
+++ b/project/plugins.sbt
@@ -2,3 +2,4 @@ libraryDependencies += "org.scala-sbt" %% "scripted-plugin" % sbtVersion.value
 addSbtPlugin("com.github.sbt" % "sbt-ci-release" % "1.5.10")
 addSbtPlugin("com.eed3si9n" % "sbt-buildinfo" % "0.11.0")
 addSbtPlugin("org.scalameta" % "sbt-scalafmt" % "2.4.6")
+addSbtPlugin("com.scalawilliam.esbeetee" % "sbt-vspp" % "0.4.11")