POM fails to validate with error "Developer information missing"

[edenman]

I was missing those keys (had them under an old name). Would be cool if we could validate the generated pom.xml with whatever tool Sonatype is using

[gabrielittner]

I think we can do that once we stop adding mavenCentral/sonatype as the default publishing target (current release + 2, because the current behavior will be deprecated first). Adding checks like this would be a lot easier then.

[gabrielittner]

There are no more blockers for this. When publishing to maven central gets enabled we can register a task for each MavenPublication that depends on the pom generation task and gets the pom input. The pom can then be parsed using the same library that we use already in the integration tests and we can check if all required elements are there. Sonatype lists those requirements here https://central.sonatype.org/publish/requirements/#sufficient-metadata (more or less).

There are 2 options for wiring up the new task. We either make check depend on it so that regular CI runs catch if something is wrong. The alternative is to make the individual publish tasks depend on our validation task so that publishing fails before uploading. It's also an option to do both.

Side note: Since 0.22.0 we are also printing Sonatype errors that happened while closing the repository directly during the build. So at least you won't have to go to the website anymore in most cases to see what the issue was.