Add configuration for new publishing process to Central

[rzo1]

This PR reconfigures the release process to use the new Sonatype Portal after the namespace was migrated.

FYI: @reckart @mawiesne

[rzo1]

Any update @reckart ? We would need that in a released version to run a new jwpl release

[reckart]

The question remains: can I still publish to non-central repositories when this change has been made? E.g. when I publish INCEpTION, it goes to a repository hosted by UKP Lab. Do you know if that will still work?

[rzo1]

Nope. You could try? ;-) (or we put it into an additional profile)

[reckart]

@rzo1 I'll have to release it then with this change, don't I - since I can't release INCEpTION based on a SNAPSHOT parent.

Here is my hypothesis:

• central-publishing-maven-plugin is an extension that overrides the default binding of the maven-deploy-plugin to the deploy phase
• so if I apply it as is, INCEpTION won't be able to release to the UKP repo anymore (unless the central-publishing-maven-plugin is somehow smart and supports "legacy" repositories")
• since the central-publishing-maven-plugin is an extension, it cannot be put into a profile because (afaik) extensions need to be activated before profiles are evaluated

So the thing seems on hinge on whether the new plugin supports legacy repositories. Unfortunately, I didn't find any documentation on that matter.

[reckart]

Well, anyway. I'll merge it, release it, and then we'll see.

[reckart]

Oh, I forgot to mention - the bad thing about extensions inherited from a parent POM is that they (afaik) cannot be disabled by the inheriting POM. So the alternative to a profile would be to have to put an .mvn/extensions.xml into the repos that wanted to use this extension.

[reckart]

33 has been published using the new process. I'll try INCEpTION in a bit.

[reckart]

Ok, so the with the plugin present, I can no longer deploy to non-maven-central. That's not nice.

I upgraded INCEpTION to 33 and ran a release build, and instead of respecting the distributionManagement section, it simply uploads to Maven Central.