New artifact name

[ashawley]

I noticed that the artifact name was changed to scalacheck-1.14. It was previously set to scalatest-scalacheck. Was this intentional? The convention for most Scala packages that provide extensions to upstream projects is to prefix their package name and suffix the upstream project. It probably helps avoid confusion about whether the project is a fork, or just an integration of a project.

[ashawley]

Also, there are a number of projects using the previous name:

https://mvnrepository.com/artifact/org.scalatestplus/scalatestplus-scalacheck

[sloshy]

To add to this: the new name is really incompatible with how people are updating packages these days with scala steward. Say Scalacheck bumps up to 1.15.x, how will I know there's a new version since the artifact name will likely change as well? I'll have to find out through other means rather than using an SBT plugin or relying on scala steward to make an MR for me.

[ashawley]

That's less of a concern. The ScalaTest team needs a way to support multiple minor versions of ScalaCheck, so adding the ScalaCheck version name to the artifact name probably makes sense.

[ashawley]

While upgrading the Scala Community build to ScalaTest 3.1, @SethTisue ran in to this issue.

scala/community-build#1044