Wrong artifactId in generated pom.xml when publishing to maven repositories

[domdorn]

This came up when we tried to make sbt download all our dependencies through JFrog Artifactory on the example of sbt-spotless ( moznion/sbt-spotless#29 )
Long Story short: The generated pom.xml does not include sbt-versions + scala-versions in the artifactId.
E.g. the artifactId is sbt-release instead of sbt-release_2.12_1.0

This results in Artifactory blocking the download which in turn results in failing to download the whole plugin in sbt.
This in turn results in being unable to use the plugin in a corporate environment where all dependencies need to be resolved through the central dependency proxy.