pom file created in staging is stripped of <developers> entry, cause unknown about sbt-sonatype HOT 3 CLOSED

@michael-card I guess you need

publishMavenStyle := true

setting

from sbt-sonatype.

we already use that setting. As it turns out Iyou can close this issue because the problem was a change in the publishing logic at Sonatype (maybe a change in the Nexus code?) We had to set up a custom staging policy that would not run validation rules on .pom files so we could release. They are still running down what had changed since 8/5/2017 when our repo last published successfully with sbt-sonatype version 2.0. Since I was unable to publish this exact same repo which had not changed and was still using sbt-sonatype 2.0, the change that broke things had to happen in Nexus or someplace else, not the plugin.

from sbt-sonatype.

Actually sbt-sonatype doesn't modify the publishing step of sbt, so you should ask this type of questions in:
https://stackoverflow.com/questions/tagged/sbt
, or use sbt-pgp issue list.

Let me close this ticket.

from sbt-sonatype.