eugene yokota

I'm in the process of creating a dedicated GitHub account for this, since I don't think putting my own token is a good idea. The GitHub account that I created...

This is, to some degree an intentional design because Maven doesn't have the notion of extra attribute that we can use as resolution axis (i.e. same version, but different X,...

Does that translate to correct `ivy.xml`? What would the `name` say in https://oss.sonatype.org/content/repositories/public/com/lucidchart/sbt-scalafmt_2.12_1.0/1.10/sbt-scalafmt-1.10.pom?

I don't think we can fix this till sbt 2.x because the layout is built into https://github.com/sbt/sbt/blob/1.x/launch/src/main/input_resources/sbt/sbt.boot.properties and ```scala def mavenStyleBasePattern = "[organisation]/[module](_[scalaVersion])(_[sbtVersion])/[revision]/[artifact]-[revision](-[classifier]).[ext]" ``` so all plugins will need to...

> FTR, I'm not saying we should add a new resolver. In fact, no new resolver is needed. The value of publishing sbt plugins to maven repos is that you...

Let's summarize: 1. Central - no problem 2. Ivy layout on personal Bintray or sbt community repo - no problem 3. Companies using Sonatype or Artifactory internally - no problem?...

Right. So publishing should be customized also with sbt-bintray for plugins with a big warning sign saying that all users would also need sbt-bintray (and thus not recommended for OSS)...

If you're suggesting we add a _second_ Maven Central resolver, I am against it. For all other personal or corporate Bintray usage, it doesn't need change in sbt.

I agree it's an unfortunate behavior on sbt's part, but the true fix requires sbt 2.x, and as far as the majority of the users are concerned, it's been working...

FWIW Artifactory publishing using sbt 0.13 also required "Supress POM Consistency Checks."